IDENTITY-CONTRACT: three statements a reader would take as fact, corrected

G-1 records the standing lesson for this document: an interface document should contain no statement a reader will take as fact when it is not yet one. Three remained in it. Section 2 chain diagram read DECIDES against CT 101, which decides nothing and sets no header. Section 5 routing table listed /m/stl as members. Section 5 stated flatly that export is gated today. Section 8 said the opposite of all three, further down, where an outside implementer would reach it second.

None of the three is now removed or softened. The scheme stays and each says which it is - where the line falls once enforced, not where it falls now.

README: deploy/ added to the layout, absent since 12 SEP. The reading order no longer contradicts PROCESS section 8 and HANDOFF section 0, and points at DIVERGENCES.md. The AGPL section 13 obligation is marked not met, stated in the document that states the obligation.

ACCEPTANCE section 7 records that its correction finally landed in HANDOFF section 7, and why parking a correction in a second document is a bad pattern: it sat here for three weeks while the wrong numbers stayed where people read first.

Applied by anchored patcher. Suite 643 passed, oracle intact. Documentation only.

README.md

@@ -30,6 +30,7 @@ do not want to be bound to. Measure and attest; never adjudicate.
 
 ```
 docs/                     specification, state, failure log, roadmap
+deploy/                   service unit and vhost, under version control
 legacy/openscad/          rev 8.0.0 generators — reference, not a live target
 fixtures/                 frozen acceptance oracles
 tools/reference-toolchain/  pinned OpenSCAD + BOSL2, build-time only
@@ -37,10 +38,14 @@ src/mechcomp/             the application
 tests/                    acceptance against the oracle
 ```
 
-Read `docs/ROADMAP.md` first for what this is, then `docs/ENVIRONMENT.md` for
-how an instance is built. If you are writing provisioning automation, read
-`docs/FAILURES.md` **before** the specification — every entry is something a
-script written from the specification alone would have got wrong.
+Read `docs/ROADMAP.md` first for what this is, then `docs/PROCESS.md` before
+issuing any command against a host. `docs/HANDOFF.md` §0 and `docs/PROCESS.md`
+§8 both carry the full reading order and are kept in step with each other.
+
+If you are writing provisioning automation, read `docs/FAILURES.md` **before**
+`docs/ENVIRONMENT.md` — every entry is something a script written from the
+specification alone would have got wrong. `docs/DIVERGENCES.md` lists the
+requirements that are specified and not currently met.
 
 ## Getting started
 
@@ -83,3 +88,8 @@ AGPL-3.0-or-later. See `LICENSE`.
 Section 13 obliges us to offer source to users interacting over a network, so
 any deployed web tier carries a visible link back to this repository. That is a
 licence obligation, not a courtesy.
+
+**It is not currently met.** The composer has been publicly reachable since
+2026-09-11 and the served page carries no such link. Recorded as DIV-001 in
+`docs/DIVERGENCES.md`, where it is the first item on the list, and required
+again as constraint 11 in `docs/ENVIRONMENT.md` §14.