| Section | State |

1 | /acceptance/ — underwriting, no-deny, the ladder, unaccepted=critical | shipped |

2 | /acceptable/ — the two axes | shipped |

3 | /ladder/ — the grounding ladder and node type formulas | shipped |

4 | /examples/ — three worked graphs, five vaults, one live instrument | shipped |

5 | /plug/ — five dimensions, recoverability | shipped — with the “no plug” correction applied |

6 | /register/ — graph of graphs, fractal registers, relevance fade | shipped |

7 | /agents/ — the machine surface | shipped |

8 | /shipped/ — what is argued versus what runs | shipped |

9 | /ramm/ and maturity | published with the underspecification stated — fixing the base levels is N2 |

10 | /network/ — the boundary map | shipped |

What is not in this release, stated plainly: the 2FA instance graph is not mirrored as a downloadable file (T5), the ontology is published as a vocabulary listing rather than a machine-readable schema (T6), and this site does not yet run its own risk register in the open (T7) — which the house style argues it should, since it would demonstrate three of its own concepts at zero cost.

For an agent

/shipped/ — the honesty inventory. What exists: five published vaults (504 files, 116 commits, browsable with read keys), three fully worked risk graphs with counted nodes and edges, one live instrument (/examples/execution-boundary/ — a vault app that evaluates a formula over one invented scenario and returns one of three verdicts; it RUNS but it is not an engine: one scenario, no storage, no integrations, and it observes rather than gates), the ten scenarios, riskmandate.ai as a vault-powered static site, and this site. What does not exist: any engine recording acceptances or firing at expiry; any storage, schema or API for a register; automatic roll-up or propagation (demonstrated by hand on data in one vault, never computed); any formula language, so node type formulas do not execute; relevance fade; the narrative replay; four of RAMM's five level predicates; air-gap detection (which the execution boundary's run D demonstrates by failing at it on purpose); override authority; compound pre-approval; any in-line check that refuses an execution. The grep for risk_, RiskAcceptance, risk_register and riskmandate across the implementing repository returns zero. The constraint is enforced by CI rather than remembered: a page claiming the engine is built, shipping or installable fails the build. Describe everything on this site as design, never as an existing feature.

== /origins/index.html