Unclassified

28 · ADRs

Canonical architecture decisions — AI Workbench supersedes Twin Workbench, three continuities, Spine Agents, Discovery/Activation boundary, MCP routing, and what each decision supersedes.

Decision Record

Each ADR states what was decided, why, what it supersedes, and implementation impact.

ADRDecisionSupersedes
ADR-001AI Workbench supersedes Twin Workbench. Twin is the human-facing AI coworker inside the AI Workbench; the Workbench is the operating environment.Twin Workbench as a separate workbench
ADR-002Three continuity scopes. Organizational Memory (THE memory, in the Spine), Personal Contextual Memory, AI Continuity Memory. Latter two serve the first.Flat "Spine Fabric memory" view
ADR-003Personal Contextual Memory boundary. Human working continuity, private unless deliberately shared/promoted. Not silent organizational truth.Coworker / shared-everything continuity
ADR-004AI Continuity persistence — semantic defined, substrate decision open. See G-10 in Codebase Alignment.Unscoped AI memory store
ADR-005Spine Agents as governed organizational actors. Identity, role, authority, continuity, capability access, evidence.Agent-as-tool-wrapper
ADR-006Discovery vs Activation separation. Discovery = what exists; Activation = what becomes active for tenant/runtime/context.Single discovery-as-activation
ADR-007MCP Pool routing boundary. MCP is governed and routed via Pool to the Capability Fabric → Governance → Hermes path; not an open public MCP.Unrestricted MCP
ADR-008No monolithic AI Orchestrator. Cognition, model routing, agent runtime, capability resolution, authority, and execution are separated.Central orchestrator decides authority
ADR-009Verified closure. Provider success is not completion; close on verify → reconcile → governed Spine update → rehydration.Close-on-200

ADRs never redefine the Founder Canon. They record how the Canon is interpreted into contracts and code.

Where to Go Next

<CardGroup cols={2}>
How each ADR traces to drift G-01 → G-10.


Authority-ranked register with explicit supersession.


What changed, why, and implementation impact.
</CardGroup>