This hub gathers how aswritten's system is structured across infrastructure, tooling, and perspective. The mainline is a layered infrastructure account: the [canonical architectural model] (Obs_ArchitecturalModel) names Identity, Auth, Sources, Storage, Credentials, and Transport, with [every user backed by a managed repo] (Narrative_ManagedRepoPerUser) as invisible infrastructure. Workflow and folder structure map onto this — a [folder taxonomy] (Obs_FolderTaxonomy) of Entrypoints/Flows/LLM/Repo/Comms and a [six-workflow taxonomy] (Obs_WorkflowTaxonomy) separating side-effecting Flows from pure functions. The agent-facing surface is the [three-tool architecture] (Obs_ThreeToolArchitecture): compile, introspect, scope. Forward-looking, a [triple-store convergence thesis] (Narrative_TripleStoreConvergence) argues OOM, compile reliability, and production-scale context are one problem solvable by Jena/Fuseki or DreamDB-inspired storage. Distinct from all the plumbing, the [named-perspective-as-sub-agent claim] (Claim_NamedPerspectiveAsSubAgent) (dated 2025-07-14) holds that an advisor's curated take operates as its own sub-agent. Two style observations debate where the architecture's canonical statement actually lives — code block versus markdown table.
Witness phrases
verbatim Identity (Outseta), Auth (JWT), Sources (integrations), Storage (one repo per memory), Credentials (Datomic internal API), Transport (single /mcp adaptive).
verbatim compile (session bootstrap, full org context, compressed snapshot), introspect (analytical, gaps/tensions/questions), scope (content retrieval, full-depth subgraph for arbitrary focus).
verbatim Every user gets an owner/repo managed entirely by aswritten — the repo is invisible infrastructure
verbatim A triple store architecture converges three distinct problems into one solution
verbatim it is a curated sub-perspective that represents the advisor's particular take, distinct from the root organizational perspective
verbatim Storage substrate is unsettled: the canonical model commits to GitHub repos plus a Datomic internal API, while the convergence thesis proposes a Jena/Fuseki or DreamDB-inspired triple store — different foundations coexisting.
verbatim The named-perspective-as-sub-agent claim is a structural outlier — it concerns perspective/agent semantics, not the infrastructure layering that dominates the rest of the hub.
verbatim Two competing claims about where the architecture's definitive statement lives — a fenced code block versus a markdown table, each asserted as 'not the prose.'
verbatim The model is labeled 'five-layer' but enumerates six roles (Identity, Auth, Sources, Storage, Credentials, Transport) — an unreconciled count discrepancy.
In this area
ClaimClaim_NamedPerspectiveAsSubAgent Scarlet [30:41]: 'In the planning session for any particular task, like, I want to know what Tony thinks as Tony has represented, you know, your... And our sort of shared opinion over every call we've had.' The named perspective is not a fl
NarrativeNarrative_ManagedRepoPerUser Every user gets an owner/repo managed entirely by aswritten — the repo is invisible infrastructure
ObservationObs_WorkflowTaxonomy Six new workflows created across four architectural roles: Flows (orchestration with side effects at edges), LLM Pure Functions (no side effects), Comms (external communication), Entrypoints (webhook normalization).
StyleObservationStyleObs_CodeBlockArchDiagram Fenced code block used for architectural model summary — columnar label:value alignment. Treats architecture as readable artifact, not prose.
StyleObservationStyleObs_TableDrivenArchitecture Markdown tables used to crystallize architecture decisions: the three-tool table (Tool | Purpose | Returns) is the definitive statement of the architecture, not the prose.
2 further nodes are not published in the public projection. Each node links from the entity index.