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
I1022
Drift in any derived surface fails the build
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
4- Waiting on
- Holds back
- Behind it in all
2- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1007 | I1007 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Extend the generation check to cover every artifact this milestone introduces — the graph, the static projection, the navigation, the indexes, the search data — so a stale committed projection cannot merge.
- Why
- Generation without a check is a suggestion. This is the mechanism that makes every derived surface in this milestone actually derived.
- Now
- The generation check covers the existing target set.
- Wanted
- The new artifacts are in the same set, and a drift failure names the source to change rather than the file that differs.
- Done when
- unknown: the record declares no `completion`
- Risk
- A non-deterministic generator turns this check into noise within a day, and the response to noise is to disable the check.
Acceptance
- Every new artifact is part of the canonical target set and its check
- A drift failure names the authoritative source to change, not only the generated file that differs
- Generation is deterministic, so an unchanged repository never reports drift
- CI executes the check on every change
- Validation
majordomus generate --checkbash test/run.sh- Evidence required
drift_coveredsource_named- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/generate.rs- Not
A separate drift script for the new artifacts- Depends on
- Priority
- p0
- 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-06
- Updated
- 2026-09-06
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
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.