This hub aggregates [novelty assessments] (RubricAssess_Novelty) evaluating the originality of framing, terminology, and metaphors across organizational artifacts. The thematic span consistently highlights a departure from generic SaaS and AI-hype language, favoring [fresh conceptual architectures] (RubricAssess_Novelty) like 'worldview as executable strategy' and 'narrative source of truth'. Assessors frequently contrast this [distinctive positioning] (RubricAssess_Novelty_1) with the [technical-narrative integration] (Assess_Novelty_collective_memory) of Git-as-log, noting how [IP-centric framings] (Assessment_Novelty_IPCrisis) ('cultivation trap', 'context squishing') avoid common domain boilerplate. While [ADR-specific assessments] (RubricAssess_Novelty_ADR002) acknowledge the necessity of conventional formats, they praise the avoidance of generic 'AI memory' labels in favor of 'worldview layer' terminology. Across the board, the [GTM voice] (RubricAssess_Novelty_GTM) and [expert-bottleneck framing] (Assessment_Novelty_CustomerArchitect) are credited for their high type-token ratio, though assessors consistently flag residual 'stock' phrasing—such as 'source of truth' or 'pilot-to-expand'—as the necessary cost of maintaining clarity within these novel structures.
Witness phrases
verbatim worldview as executable strategy
verbatim IP crisis vs developer convenience
verbatim narrative source of truth
verbatim senior expert bottleneck
verbatim Worldview layer
verbatim ADR documentation is explicitly noted for its reliance on conventional business language, contrasting with the high-novelty creative artifacts.
verbatim Some assessments identify a tension between 'fresh metaphors' and the inclusion of domain-standard phrases like 'pain-first' or 'four pillars'.
In this area
RubricAssessmentAssess_Novelty_cm Novel architecture patterns (State abstraction, Memory decomposition); some standard technical documentation phrases; Mermaid diagrams add visual novelty
RubricAssessmentAssess_Novelty_collective_memory Novel integration pattern (two-step save); creative use of Git as narrative log; fresh framing of 'Memory' as ephemeral input vs 'Transaction' as durable change; avoids generic SaaS architecture clichés
RubricAssessmentAssessment_Novelty_CustomerArchitect Fresh framing ('senior expert bottleneck' vs. 'AI memory lock-in'); some domain-standard phrasing ('signs the checks', 'locked in heads'); overall avoids cliché.
RubricAssessmentAssessment_Novelty_IPCrisis Fresh framing (IP crisis vs developer convenience); novel terminology (compilation targets, cultivation trap, context squishing); avoids generic AI hype language
RubricAssessmentRubricAssess_Novelty Original phrasing ('narrative architecture,' 'steering vector,' 'resonant body') and fresh metaphors. Avoids most startup clichés. Some generic constructions ('product market fit,' 'first principles') but used purposefully. High type-token
RubricAssessmentRubricAssess_novelty Fresh framing (git for narrative); distinctive brand voice; some stock phrases ('source of truth'); overall original positioning
RubricAssessmentRubricAssess_Novelty_1 Novel framing: 'narrative source of truth', 'individuation pipeline', 'evolved variant', 'collective memory marketplace'. Distinct from generic AI memory/RAG positioning.
RubricAssessmentRubricAssess_Novelty_ADR001 Standard ADR format (expected); business language conventional; 'collaborative worldview layer' phrase somewhat novel; overall appropriate level of originality for decision record
RubricAssessmentRubricAssess_Novelty_ADR002 'Worldview layer' positioning is fresh vs. generic 'AI memory'. '[amount] mistake' quantifies pain memorably. Avoids boilerplate; specific tool names (Claude Code, Cursor) add authenticity.
RubricAssessmentRubricAssess_Novelty_GTM Fresh framing ('state secrets', 'IP as code'); some standard GTM structure (pilot→expand); avoids clichés; distinct voice.