This hub tracks the evolution of process and policy, centering on the [perspective-vs-implementation boundary](https://aswritten.ai/narrative#Narrative_PerspectiveVsImplementationLine) established in April 2026. This principle dictates that while perspective captures intent, reasoning, and directional logic, the repository remains the domain for literal configuration and specific identifiers, a distinction reinforced by [Position_PerspectiveHoldsIntent](https://aswritten.ai/narrative#Position_PerspectiveHoldsIntent). Parallel to this, the [research branch as temporal isolation](https://aswritten.ai/narrative#Narrative_ResearchBranchTemporalIsolation) strategy emerged as a pragmatic alternative to complex ontology, favoring [branch-at-root](https://aswritten.ai/narrative#Obs_ScarletBranchAtRootQuote) as a \"boring-and-works\" mechanism. This approach, supported by [Position_ResearchBranchMethodologyDecision](https://aswritten.ai/narrative#Position_ResearchBranchMethodologyDecision), defers structural experiments in favor of stability. Earlier foundational shifts include the [product-wide pattern of prompting in return values](https://aswritten.ai/narrative#Narrative_ReviewReturnValuePattern), which integrates reinforcement directly into tool feedback loops rather than relying solely on upfront descriptions. These policies collectively prioritize operational stability and clear separation of concerns over experimental architectural complexity.
Sub-areas
Narrative PerspectiveVsImplementationLine7 nodes 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 inten…
Witness phrases
verbatim Perspective holds decisions and reasoning; implementation holds literal detail; both are knowledge but belong in different places
verbatim this isn't the right time for ontology and repo structure experiments.
verbatim Boring-and-works beats clever-and-risky at launch.
verbatim doing more prompting in the return values from tools instead of always just up front in the tool descriptions.
verbatim I think branch should be optional, and it should default to main.
verbatim Tension exists between the desire for branch-optionality and the current reliance on long-lived research branches.
In this area
Narrative_ResearchBranchTemporalIsolation Research Branch as Temporal Isolation via Versioning
NarrativeNarrative_ReviewReturnValuePattern Prompting in Return Values: Product-Wide Shift in Agent Communication
ObservationObs_ScarletBranchAtRootQuote Scarlet's decision to use branch-at-root over subdirectory scoping — the boring-and-works principle applied to temporal isolation.
ObservationObs_ScarletBranchPolicyQuote Scarlet's statement on branch defaulting to main with context-dependent guidance.
ObservationObs_ScarletNotRightTimeQuote Scarlet's explicit rejection of ontology and repo structure experiments mid-launch — the rationale for deferring narr:appliesAs.
ObservationObs_ScarletReturnValueShiftQuote Scarlet's canonical statement of the product-wide shift toward prompting in return values.
2 further nodes are not published in the public projection. Each node links from the entity index.