Founder walkthrough

Primitive in one sitting.

Follow this in order. Each page starts simple, then lets you go deeper. The full tour is about 85 minutes; stopping after step 8 gives a strong 44-minute operating mental model.

How to use this together: read the TL;DR aloud first. If the gist is clear, look at the diagram. Only expand into the tables/technical detail when one of you asks “but how does that actually work?”
01
Start with the whole system4 min

Workspace does the work, Control governs the work, Foundry governs intake, Ohio preserves constitutional lineage, Docs explains.

→
02
See how information moves4 min

Inboxes are append-only; typed Signals carry urgency/impact/authority requirements; escalation does not grant authority.

→
03
Understand the orchestrator6 min

The orchestrator coordinates packets, claims, model selection, independent review, CI, merges and receipts — it is not the whole workforce.

→
04
Understand Holarchy6 min

0–3 direct authority-bearing children, bounded rolling topology, adaptive OPEN/FOLD/PARK/CLOSE. Three is a cap, not a quorum.

→
05
Understand constitutional identity6 min

Ohio preserves lineage and forward-only history; Right of Return restores the Genesis Parent seat without rewriting history or seizing descendant lanes.

→
06
See how Primitive learns from its own work5 min

Hermes is a sidecar observer, not a child orchestrator. Raw observations stay local; only evidence-backed lessons are promoted.

→
07
See how fast routing works6 min

Reflex selects a bounded expert/context/tool set and can abstain/escalate. It never grants execution authority.

→
08
Separate Memory, Context and Knowledge7 min

Memory is retained, Context is selected for this task, Knowledge is reviewed/accepted. They must not silently collapse into one another.

→
09
See where information enters7 min

Foundry discovers/tags/reviews/seals; Google Drive is the promoted knowledge baseline; OS receives a versioned bundle after approval.

→
10
Learn the tagging grammar8 min

Preserve source identity first; add filing, relationships, memory/evidence/context metadata as derived layers with provenance.

→
11
Understand the maths8 min

One canonical E/P/A 27-state cube today; E/R/C shadow charts and the 3^7 coordinate are experiments, not production facts.

→
12
Understand model routing7 min

Cheap-first, evidence-driven routing; data class/privacy and independent reviewer family outrank model popularity.

→
13
Check what is actually proven7 min

Experiments are tracked by evidence state; working theory is visibly separated from implemented/runtime facts.

→
14
Use the vocabulary6 min

Domain ≠ Scope. Role ≠ Authority. Zero ≠ UNKNOWN. Captured ≠ Canonical.

→
After the tour

Use Docs as a map, not a second source of truth

When a page matters operationally, follow its Reference / evidence section into Control, Workspace, Foundry or Ohio. Docs is designed to make the system understandable and searchable while preserving the actual authority boundary.