A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I1408
The documents stop claiming a projection nobody runs
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- VERIFY
- Wave
3- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- 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.
- Now
- 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.
- Wanted
- 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.
- Done when
- unknown: the record declares no `completion`
- Risk
- Low.
Acceptance
- 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-checkmajordomus doctrine- Evidence required
claims_cite_gates- Evidence present
claims_cite_gates
Scope
- Touches
docssite.ai/repo/project/README.md.ai/repo/project/project.yaml- Not
Weakening a claim that the gates do support- Depends on
- Priority
- p2
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-09
- Updated
- 2026-09-09T17:50:40Z
- Started
- 2026-09-09T17:50:11Z
- Verified
- 2026-09-09T17:50:29Z
- Completed
- 2026-09-09T17:50:40Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.