The matters of note

OX shows what is; this page offers what is not yet — the OOI's planned and designed but unfinished business, presented as good for contribution. This is the ingress diode: reading is free; the way across is a statement of intent, on the record.

The honesty register. Statuses are operator-declared as of 2026-07-31 — DESIGN designed but unbuilt · PARTIAL partly built · OPEN identified, not yet designed. Nothing here is auto-asserted from a scan; a wrong status is a discovery and gets corrected on the record. Some covering documents are held on the private origin — the matter stands either way.

id	the matter	area	status	delivered means
`a1-ratchet-resync`	Federation ratchet skipped-key resync window The single largest federation blocker — nothing federates without it: the resync window for skipped ratchet keys between real peers. covering doc: `federation-clustering-design.md` · source: roadmap T1-A1	federation	DESIGN	two peers survive dropped/reordered frames and re-converge without re-genesis
`a2-node-transport`	Real node-to-node transport + federation daemon A QUIC- or WS-stream-per-edge transport and the daemon that runs it; today the mesh is designed but in-process only. covering doc: `federation-clustering-design.md` · source: roadmap T1-A2	federation	DESIGN	a channel between two hosts over a real network
`b1-two-ox-bridge`	The two-OX [ENDO] bridge A channel over the union graph with correct Triadic Closure and bridged gossip — the first true peer link (the root handshake A0 is built; this is the next rung). covering doc: `federation-clustering-design.md` · source: roadmap T1-B1	OX	DESIGN	two OX nodes exchange witnessed state end-to-end
`c1-access-hierarchy`	The access-control hierarchy Prime-seed bootstrap; Superadmin/Experimenter/Participant genesis replacing the static boundary token (the grant envelopes are built; the hierarchy is not). covering doc: `access-hierarchy-design.md` · source: roadmap T1-C1	OX	DESIGN	the static token retired; roles genesis-derived
`c1a-causal-actor-iam`	Causal-actor IAM — person ingress A person as a causal actor: the OaOooa device as ingress (the A0 handshake at person scale); identity verified by FDV over immutable CKAN datasets. covering doc: `causal-actor-iam-design.md` · source: roadmap T1-C1a	OaOooa	DESIGN	a person's acts carry verifiable standing
`d1-causal-alu-stages-4-5`	Causal ALU stages 4–5 The 5-stage ladder's last two rungs (indifferential · max_surprise); stages 1–3 are built and live at /alu. covering doc: `oxexp-causal-set-design.md` · source: roadmap T2-D1	OX	PARTIAL	the full ladder resolves on the live instrument
`d2-ckan-phases-2-5`	CKAN integration phases 2–5 Per-experiment ckan grants, experimenter visibility, participant preflight, member read; phase 1 (the granted server resource) is built. covering doc: `the CKAN integration plan` · source: roadmap T2-D2	OX	PARTIAL	role-aware portal access end-to-end
`d5-metabolic-alignment`	Metabolic-alignment loop at WAN scale Cross-stratum bond tuning over a real network — identified, not yet designed. covering doc: `federation-clustering-design.md §8.1/§12` · source: roadmap T2-D5	OX	OPEN	a designed loop with sealed probes
`d6-ci-coverage`	CI + coverage as a merge gate An automated pipeline running the physics-conformance suite as a merge gate; the per-file suites pass by hand today. covering doc: `the tests/ suite + run_all_tests.py` · source: roadmap T2-D6	CX	PARTIAL	a pipeline that refuses a regressing change
`d8-persona-docs`	The persona documentation set User / Sysadmin / Maintainer / API / Extending / Theming / Contributing / Changelog — the CKAN-style docs ladder for every persona. covering doc: `the sysadmin lifecycle note + ooi_docs/` · source: roadmap T2-D8	SX	DESIGN	a reader per persona finds their path
`lm1-build2-grounding`	OaOooa BUILD 2 — the grounding act present() on-device via the EAS dev-client: the participant's grounding act (present → attest → confirm) in the shipped app; BUILD 1 (the jurisdiction + modules) is live. covering doc: `oaooa-jurisdiction-sync-and-modules-design.md` · source: review §5 LM-1	OaOooa	DESIGN	a device earns standing by its own act (seal LM1-S5)
`lm2-s3-intent`	LM2-S3 INTENT — the witnessed statement of intent Publish → export → H_intent → the FDV binding → the verifiable when. CLAIMED BY THE ALPHA-13 CAMPAIGN (the public-edition design §7a) — listed here so the claim is on the record. covering doc: `sx-prior-art-and-port-design.md §3 + alpha-12-13-public-edition-design.md §7` · source: review §5 LM-2 · roadmap T2-D3	SX	DESIGN	a new SoI version witnessed end-to-end; re-verification re-derives
`lm2-s4-node-join`	LM2-S4 NODE-JOIN — the first non-root node dev.opendata.ly attests to dev.opendata.ai via the built A0 handshake and appears with standing on /federation/nodes; standing starts at I under trust-decay. covering doc: `sx-prior-art-and-port-design.md §4` · source: review §5 LM-2	SX	DESIGN	the SX node visible in the trust network
`lm2-s5-accord`	LM2-S5 ACCORD — 1 locks 2 Two personas' intents resolve within ONE accord record; the founding instance: starl3n × Link Digital; the accord's fitness consideration IS the synthetic-agreement instance. covering doc: `sx-prior-art-and-port-design.md §4` · source: review §5 LM-2	SX	DESIGN	the founding accord recorded and readable
`sxexp-build2-act-store`	The deliberate-act witness store (sxexp BUILD 2) POST /sx/act — the anonymous deliberate-act ledger for the understanding experiments (fail-closed 422; NO identity seat; the run windows seal before they open); BUILD 1 (the instrument pages) is live. covering doc: `sx-understanding-experiments-design.md §7` · source: the sxexp design §7	SX	DESIGN	Experiment #1 runs measured, E-only
`contest-board-and-referee`	The Contest — the board and the referee The OOI's standing form for challenging held knowledge — its own included. THE BOARD: the baselines table (seven baselines, binding symmetrically on the house and every challenger), the stake ledgers (every staked claim with its named kill and return line), the open workshop, and the wall. THE REFEREE: the record, never a person — the seal that precedes the read, the kill kept, the anchor beyond edit-reach, the walk against pre-committed criteria; the only scorekeeper neither position can flatter. covering doc: `sxexp-constructs-design.md §4g` · source: Dialogues at the Wall (seal 77547b9); the operator's grant 2026-07-31	SX	OPEN	a challenge lodged under the seven baselines and landed as-sealed — kept with full standing whatever it shows

The statement-of-intent path (v0 — recognition over replacement)

Read the matter above, and its covering document where available.
Write your statement of intent — who you are (a persona, however young), which matter, what delivered would mean in your hands, and over what period.
Lodge it at the inbox: open an issue on github.com/starl3n/ooi-ox titled SoI: <matter-id> (e.g. SoI: lm2-s4-node-join). The inbox is where an intent is offered — it is not a write path into the accord.
The operator recognizes it — a row on the founding sheet (the sheet remains the only statement-of-intent write surface in v0); it then ingests here as recognized.
At Alpha 13 it is witnessed — witnessed-at-publish (H_intent + the FDV when) — and the work you deliver binds to your intent as constructs: the E-attribution edge. Your standing grows from having genuinely shown up.