Ohio, Genesis & identity continuity
The constitutional lineage layer that preserves identity, ancestry, delegation and forward-only history across forks and handoffs.
Ohio is the constitutional/lineage layer, not the day-to-day orchestrator. It defines Genesis identity, preserved ancestry, bounded delegation, continuity across forks and Joshua's protected Right of Return. Control remains the operational authority plane; Workspace remains the product/runtime plane.
Think of Ohio as the birth certificate and constitution, not the office manager. It records who came from whom, what authority was actually handed down, and how to recover the original constitutional seat if a key/session disappears. It does not run every task or erase history when people return.
The Ohio protocol treats principal identity, account/provider identity and individual executions as different things. History extends through explicit forward events; it is not rewritten. Descendants can only delegate authority they actually possess. Human-readable lane names are labels, while lineage-derived identifiers preserve canonical ancestry even if the organisational view changes.
Ohio, Control and Workspace have different jobs
| Plane | Canonical concern |
|---|---|
| Ohio | Constitutional identity, lineage, Genesis, continuity, bounded delegation and Right of Return |
| Control | Operational authority, jobs, inboxes, leases/permits, routing, merge/deploy discipline and receipts |
| Workspace | Product state, Comms, work objects, AI/runtime, Memory, Knowledge and Context |
Principal → account/provider → execution
Protected Genesis invariants
- Authority may change; history is not rewritten.
- Canonical ancestry is preserved even when organisational projection changes.
- A descendant cannot create authority outside its delegable envelope without a separate valid grant.
- Self-identification does not self-grant external/domain authority.
- Once state is legitimate shared history, corrections are forward events such as revoke, repair, supersede, reopen or deprecate.
Re-entry to the Genesis Parent seat, not hidden superuser power
The protected capability originates at Genesis, survives absence/delegation, is non-transferable/non-delegable and cannot be revoked by descendants. Successful re-entry restores constitutional standing, inspection/review rights and bounded emergency/recovery capabilities. It does not automatically seize ordinary descendant-lane decision authority, rewrite history, fabricate consensus or mint arbitrary authority.
Names can change; ancestry cannot silently change
Ohio's recursive lane protocol derives canonical lane identity from lineage and creation events rather than a fixed global slot table. Reparenting is not a silent mutation: a visible organisational move must be represented as an explicit projection/relationship while canonical ancestry stays intact.
Unbounded protocol namespace vs bounded operational orchestration
Ohio's lineage protocol is unbounded in principle: authorised lanes may create descendants subject to their delegation constraints. Control's Rule of Three is an operational topology policy that caps authority-bearing orchestrator fan-out and rolling population. The two are compatible because protocol identity and live orchestration capacity are different dimensions.
Related pages
Canonical sources
These pages are explanatory read models. Where wording conflicts with implementation or a Control decision, the linked implementation/decision is authoritative and this page should be corrected.