The architectural shift toward navigation-first interaction, initiated in mid-June 2026, centers on replacing monolithic snapshots with a [digest-driven traversal model](https://aswritten.ai/narrative#Position_NavigationDropsContextOrderOfMagnitude). This move, which reduced per-call context by an order of magnitude, aligns with [independent industry parallels](https://aswritten.ai/narrative#Position_DiscoveryConsultantHATEOASParallel) that favor link-based discovery over large-scale queries. By July 2026, this philosophy matured into a [standardized perspective response](https://aswritten.ai/narrative#Narrative_PerspectiveResponseOrderedByVolatility) structured by volatility, ensuring that stable maps remain constant while per-call focus is relegated to the end. To maintain graph integrity, the system adopted [synchronous per-message integration](https://aswritten.ai/narrative#Narrative_SynchronousPerMessageIntegration), rejecting asynchronous patterns to prevent state drift. The user experience now mirrors this machine-centric logic, with the [digest browser](https://aswritten.ai/narrative#Narrative_DigestBrowserProductSurface) serving as the primary interface for both human and agent. Finally, the team has defined a [content/commentary split](https://aswritten.ai/narrative#Narrative_ContentCommentarySplit) to distinguish between raw source material and authored reconciliation, though the write-side implementation remains a pending task.
Sub-areas
Narrative ContentCommentarySplit4 nodes The hub frames a structural distinction between two layers of knowledge representation: per-message primary source material transacted individually as it happens, and authored reco…
Witness phrases
verbatim Navigation drops per-call context by an order of magnitude
verbatim the primary way of navigating any information base... is through discovery and navigation, going link by link
verbatim Perspective response ordered by volatility: stable skeleton leads, per-call focus appended last
verbatim Integration is synchronous, per-message, and silent
verbatim Content/commentary split: per-message integration is the content layer; reconciliation is the authored commentary layer
verbatim Potential conflict between synchronous integration and MCP client limitations requiring a hybrid model.
In this area
NarrativeNarrative_DigestBrowserProductSurface The product surface is the digest browser — the human as consumer of the same collapse/expand navigation that extraction and citation already use
NarrativeNarrative_PerspectiveResponseOrderedByVolatility Perspective response ordered by volatility: stable skeleton leads, per-call focus appended last
NarrativeNarrative_SynchronousPerMessageIntegration Integration is synchronous, per-message, and silent — async breaks the individual and the deliberate feedback-in-chat decision
2 further nodes are not published in the public projection. Each node links from the entity index.