The Objective Observer Initiative (OOI) monorepo — alpha. One repository, several top-level concern-folders. Each owns its own build, maps to a deploy target, and — at beta — splits cleanly to its own repository (the seams are drawn now).

The OX core (ooi_network/, 0.14.0) is at Alpha 12, live on dev.opendata.ai: a single OX node — the frozen [ENDO] physics, the experiment platform, server governance (experiment enablement + grant envelopes), durable control-plane state, CKAN export, and the federation root handshake (a node↔root-SoA trust attestation — the first networking iteration; the peer mesh is designed, not yet built). Alpha 12 is an [EXO] / governance / federation release; the [ENDO] core is frozen.

Alpha 13 — the CX (Code Experience) pillar — is in progress, partly built and partly planned:

• Built (on dev): the code anchor (commit → seal → verify → publish to mldata) and its OOI-native re-base, the CX experiment — per-folder phase-locks that mint moment-keys at verifiable time, a durable tamper-sealed registry, byte confinement (cx-seal/cx-open), and a whole-tree release ceremony (release --soa). → cx-experiment-design.md.
• Planned (design): the unified grant × verification × RACI model — how experiment grants are applied and withdrawn on a persona's code claim × a node's verification (grants-verification-raci-design.md), the access hierarchy, the federation peer mesh, and a post-beta two-key state ratchet. The formal Alpha-13 release (persona key custody + the public push) is deliberately deferred.

Beta = single-node → networked, safe, open (the federation peer mesh + the access framework), with the [ENDO] physics already done and frozen — see roadmap-alpha-to-beta.md.

The OOI presents as three integrated Experience pillars:

• OX — Observer Experience · opendata.ai — the running servers + observers (incl. the data portal).
• SX — Social Experience · opendata.ly — human governance: how individuals and institutions formally engage with the OOI, and how their published statements of intent are monitored.
• CX — Code Experience — this codebase; contribution and extension.

The repo root also carries the dashboard entrypoint (dashboard.py), the simulators, and the Python pyproject.toml that the ooi_network package builds from — these predate the folder split and are not being relocated during alpha.

Coherence and atomic cross-cutting change in one repo while the contracts are still moving. Discipline that keeps the beta split cheap:

• Each folder owns its build config (pyproject / mkdocs.yml / app manifest); the root stays thin.
• Cross-folder coupling stays at the contract layer — the SoA OpenAPI, shared ooi_brand tokens, the glossary — not direct imports. At beta, git subtree split --prefix=<folder> extracts each with history.
• Path-filtered CI per folder (build/deploy docs on ooi_docs/**, run the Python suite on ooi_network/**, etc.).

• Documentation plan: ooi_docs/documentation-plan.md
• Engineering / design ADRs: ooi_network/docs/ (held on the private origin — not part of the public cut; the public accountability record is the code-anchor signal + lineage at mldata.opendata.ai)
• Deploy + ops: ooi_network/deploy/ (private origin)
• The public edition: ANCHOR.md (the anchor + the 2026-07-17 posture revision) · the licence: LICENSE (source-visible is not open-source)
• Good for contribution: /sx/matters on an SX node — the matters of note (planned but unfinished business) and the statement-of-intent path to work on delivery