I1408 — The documents stop claiming a projection nobody runs
Bring the prose in line with what the gates prove, and keep it there by citing the gate rather than the intention.
DONE wave 3 · p2 · implementation profile · parallel safe
Objective
Bring the prose in line with what the gates prove, and keep it there by citing the gate rather than the intention.
Why
.ai/repo/project/README.md states that the GitHub issues and milestones come from `majordomus plan`, and docs/claims/github-projection.md states the projection is generated from the canonical model. Both were true on 2026-09-04 and neither has been true since, because nothing ran the detector. A claim whose evidence is a script that exists rather than a gate that runs is the failure mode this repository names in its own why catalogue.
Current state
docs/CLAIMS.yaml line 798 and docs/claims/github-projection.md cite scripts/github-sync and test/cases/45_github_projection.sh as the evidence for a claim about live GitHub state. The test proves the adapter renders; it does not prove the remote agrees.
Desired state
Each claim about the projection cites the gate that would fail if it stopped being true, and the site says what is projected and what is not.
Scope
- docs
- site
- .ai/repo/project/README.md
- .ai/repo/project/project.yaml
Out of scope
- Weakening a claim that the gates do support
Dependencies
Acceptance criteria
- Every claim about the projection cites a gate that runs against the remote, not a script that exists
- The project README states what GitHub carries and what it does not
- No document states that a projection is current where no gate could detect that it is not
Validation
- scripts/ci/reference-check
- majordomus doctrine
Evidence required
- claims_cite_gates
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| claims_cite_gates | ci | scripts/ci/reference-check | the projection claim is split in two: github-projection covers what the adapter renders and refuses, github-projection-gated covers whether the remote still agrees and cites scripts/ci/github-check with test/cases/97_github_gate.sh; project.yaml, .ai/repo/project/README.md and docs/PLANNING.md now say that GitHub receives the projection only when somebody applies it, and name the gate that holds them together | 597ebe4 |
Risk
Low.
Timeline
- started
- 2026-09-09T17:50:11Z
- verified
- 2026-09-09T17:50:29Z
- completed
- 2026-09-09T17:50:40Z
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I1408.yaml. Read it back with majordomus plan show I1408.