Unclassified
33 · Founder Decision Register
Authority-ranked register of Founder decisions with explicit supersession — what decided what, when, and what it replaced.
Authority Rank (Highest First)
- Founder decisions dated 31 Aug 2026 + latest project conversations — product, experience, memory boundaries, Human Workbench, AI Workbench, human–AI operating model.
- Late-August SpineWorkspace consolidation decisions + master-system visual — authoritative design direction elaborating the Founder decisions.
- 1 Aug 2026 GitHub canonical freeze — implementation baseline where not superseded.
- Earlier canonical / downstream docs and code — evidence of implementation, migration state, historical design.
- External 2026 market research — category and design-pressure validation only.
When sources disagree, use this rank. A lower source never overrides a higher one.
Register
| Date | Decision | Supersedes | Impact |
|---|---|---|---|
| 31 Aug 2026 | Business Context as Tier-0 semantic foundation. Without it, no meaningful SpineWorkspace. | Feature-as-foundation views | Every doc, plane, and contract must trace to Business Context / Work / Outcome |
| 31 Aug 2026 | Spine is THE organization's memory. Personal Contextual + AI Continuity serve it. | "Spine Fabric as generic memory" | Memory boundaries, projection, promotion rules |
| 31 Aug 2026 | AI Workbench supersedes Twin Workbench. Twin is the coworker inside the Workbench. | Twin Workbench | AI view, agent runtime, ADK wiring |
| 31 Aug 2026 | Five separate views. User / Platform / Package / Pipeline / Agentic over the same Spine. | Three-view or single-view framings | Navigation, doc structure, ownership |
| 31 Aug 2026 | Verified closure. Provider success ≠ completion; close on verify → reconcile → Spine → rehydrate. | Close-on-200 | Pipeline, Hermes, reconciliation contracts |
| Late-Aug 2026 | Master-system visual as authoritative design direction | Earlier architecture diagrams | Reference Architecture |
See ADRs for how each decision became code and contracts, and Canonical Change Log for what changed and why.
Where to Go Next
<CardGroup cols={2}>What changed, why, what it supersedes, implementation impact.
One meaning per term — the vocabulary these decisions govern.
The single source that established these decisions.