I3087 — Seven statements about silence disagree with the record they cite, or name what does not exist
Bring seven statements into agreement with the records they cite and with the tree, each by editing its canonical source. (1) Rule project.never-reported-is-not-green says the trunk carried three branch-breaking defects that night, and docs/CLI.md and I1512 say the same; ADR 0037, which measured the night of 2026-09-10, says five. The forge records five failed check runs on 31285bdf5 (ci, site, rust, structure, coverage), ci being the verdict of the others, so ADR 0037's five counts failed jobs rather than defects; the agreement is reached by saying which is counted, and ADR 0037, which is accepted, is not edited. (2) The rule says each new push cancelled the run before it, while ADR 0037 records four runs of master still queued. (3) The rule tells the publication that reported cancelled as a wait for the content delivery network on the next day, with the site serving the new commit a minute later; ADR 0037 records a Pages deploy job killed by its five-minute budget while it waited for GitHub's Pages build, the publication done at 13:52:20 and the job killed at 13:56:12, on the same day. (4) docs/SURFACES.md says the rule has no x-majordomus block and that the proof graph reports it as unproven; the rule now carries x-majordomus.reviewed_because. (5) docs/EVIDENCE.md links ADR 40 to .ai/repo/adrs/0040-proof-is-a-recorded-execution-and-inputs-unchanged-is-not-proven.md, a file that does not exist; the decision is ADR 0041. (6) docs/CLI.md and rule majordomus.completion-gates name a rule majordomus.never-reported-is-not-green, which does not exist; the rule is project.never-reported-is-not-green, and the vendored rule is changed in share/standard/majordomus/rules/, where it is authored, and its vendored copy follows. (7) Milestone architecture-is-enforced cites plan/RUNTIME_BASELINE.md, which is not in the tree.
READY wave 0 · p2 · implementation profile · parallel safe
Ready. Every dependency is done, so majordomus plan start I3087 will be accepted.
Objective
Bring seven statements into agreement with the records they cite and with the tree, each by editing its canonical source. (1) Rule project.never-reported-is-not-green says the trunk carried three branch-breaking defects that night, and docs/CLI.md and I1512 say the same; ADR 0037, which measured the night of 2026-09-10, says five. The forge records five failed check runs on 31285bdf5 (ci, site, rust, structure, coverage), ci being the verdict of the others, so ADR 0037's five counts failed jobs rather than defects; the agreement is reached by saying which is counted, and ADR 0037, which is accepted, is not edited. (2) The rule says each new push cancelled the run before it, while ADR 0037 records four runs of master still queued. (3) The rule tells the publication that reported cancelled as a wait for the content delivery network on the next day, with the site serving the new commit a minute later; ADR 0037 records a Pages deploy job killed by its five-minute budget while it waited for GitHub's Pages build, the publication done at 13:52:20 and the job killed at 13:56:12, on the same day. (4) docs/SURFACES.md says the rule has no x-majordomus block and that the proof graph reports it as unproven; the rule now carries x-majordomus.reviewed_because. (5) docs/EVIDENCE.md links ADR 40 to .ai/repo/adrs/0040-proof-is-a-recorded-execution-and-inputs-unchanged-is-not-proven.md, a file that does not exist; the decision is ADR 0041. (6) docs/CLI.md and rule majordomus.completion-gates name a rule majordomus.never-reported-is-not-green, which does not exist; the rule is project.never-reported-is-not-green, and the vendored rule is changed in share/standard/majordomus/rules/, where it is authored, and its vendored copy follows. (7) Milestone architecture-is-enforced cites plan/RUNTIME_BASELINE.md, which is not in the tree.
Why
On 2026-10-21 a fact-check of the article on silence and verdicts (I3086) against its sources found these seven places. The article follows ADR 0037, which measured the night; a reader who follows its links to the rule, to docs/CLI.md or to docs/EVIDENCE.md meets other numbers, another story of the publication, a rule that does not exist and a link that resolves to nothing.
Current state
Each of the seven statements is in the tree at master 905159df7cc, as the objective quotes. The commit that records this issue brings (4), (5) and the docs/CLI.md half of (6) into agreement: docs/SURFACES.md says the rule carries reviewed_because and that the proof graph reports it as reviewed, docs/EVIDENCE.md links ADR 41, and docs/CLI.md names project.never-reported-is-not-green. (1), (2), (3), (7) and the vendored rule of (6) remain.
Desired state
Each statement says what the record it cites says, names only rules and files that exist, and the vendored rule changes only through its source.
Scope
- .ai/repo/project/issues/I3087.yaml
- .ai/repo/rules/project/never-reported-is-not-green.v1.md
- docs/CLI.md
- docs/SURFACES.md
- docs/EVIDENCE.md
- share/standard/majordomus/rules/completion-gates.v1.md
- .ai/repo/rules/vendor/majordomus/rules/completion-gates.v1.md
- .ai/repo/project/milestones/architecture-is-enforced.yaml
Out of scope
- Changing ADR 0037, which is accepted and is the measurement the others are brought to
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- No statement of the seven disagrees with ADR 0037 or names a rule, ADR file or plan file that is not in the tree
- The vendored completion-gates rule changes only through share/standard/majordomus/rules/ and the step that vendors it
Validation
- majordomus plan validate
- scripts/ci/rule-proof-check
- majordomus update --dry-run
- scripts/ci/link-check
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
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/I3087.yaml. Read it back with majordomus plan show I3087.