This hub states a single durable principle and its enforcement machinery: the line between what the perspective holds and what the implementation holds. The [perspective holds intent] (Claim_PerspectiveHoldsIntent) — decisions, reasoning, felt intent, the conceptual how — while [literal values are implementation detail] (Claim_ImplementationDetailExclusion) that live in files (tokens.json, CSS, SCSS) and must not appear in the perspective. The boundary runs *inside* 'how': directional/relational how stays up, specific values and config drop down. Two failure modes motivate the split: [authority confusion] (Claim_AuthorityConfusionFail) (repo and perspective asserting the same value, leaving canonicality ambiguous) and [staleness] (Claim_StalenessFail) (a memory asserting a value silently lies once the source file is edited). [Three diagnostic questions] (Claim_ThreeTestQuestions) operationalize routing, including the subtle case where a decision *about* a detail still belongs in perspective. The principle is framed as [durable by design] (Claim_DurabilityPrinciple), and was [encoded across four product files] (Claim_ProductFilesUpdated) plus a generated brand/ repo structure (20260414).
Witness phrases
verbatim The repo owns the value because code runs.
verbatim The file is the source of truth for the value; the perspective is the source of truth for why the value was chosen.
verbatim directional and relational how belongs in the perspective; specific values, identifiers, and config belong in the implementation.
verbatim It should be superseded only if the perspective/implementation line is explicitly redrawn by a future session. It is durable by design.
verbatim Is it a decision about an implementation detail, not the detail itself? → Still perspective.
verbatim Two distinct (non-identical) risks justify the line — authority confusion (canonicality ambiguous when both assert a value) vs staleness (perspective silently lies after file edit); an agent reasoning from only one misses the other.
verbatim Durability tension: explicitly framed as a principle, not a tactical decision, revisable only by explicitly redrawing the line — a high bar that resists ordinary session-level updates.
verbatim The boundary is not clean: a decision about an implementation detail stays in the perspective even though the value itself does not — the 'still perspective' edge case that blurs the otherwise sharp split.
In this area
ClaimClaim_AuthorityConfusionFail Authority confusion failure mode: if both the repo and the perspective assert the same hex code, downstream agents cannot determine which is canonical. The repo owns the value because code runs. The perspective's job is to tell the agent wh
ClaimClaim_DurabilityPrinciple This is a principle about how the product works, not a tactical decision. It should be superseded only if the perspective/implementation line is explicitly redrawn by a future session. It is durable by design.
ClaimClaim_ImplementationDetailExclusion Specific code functions, color values, layout specifics, type scale multipliers, hex codes, SCSS assignments, and config values are implementation details. They live in files (tokens.json, CSS, SCSS) and change without discussion. They must
ClaimClaim_PerspectiveHoldsIntent The perspective holds decisions, reasoning, felt intent, and the conceptual how. The implementation holds the literal detail. The line runs inside 'how': directional and relational how belongs in the perspective; specific values, identifier
ClaimClaim_ProductFilesUpdated The perspective vs. implementation principle is now encoded in memory-creation prompts across four files: CLAUDE.md (what makes a good/bad memory), ASWRITTEN.md (same plus Memories intro), resources/tool-descriptions/remember.md (tool descr
ClaimClaim_StalenessFail Staleness failure mode: a memory asserting a specific value (e.g., 'the gold is #CDA349') becomes incorrect the moment the source file is edited, causing the perspective to lie without anyone noticing. The file is the source of truth for th
ClaimClaim_ThreeTestQuestions Three diagnostic questions: (1) Could this be restated as an intent, decision, or relationship with a person behind it? → Perspective. (2) Is this a numerical value, code identifier, or config that means nothing outside its file? → Implemen