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
I2748
The drift already on the trunk is settled before the gate is made blocking
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
2- Waiting on
- Holds back
- none
- Behind it in all
0- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I2741 | I2741 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Run plan.drift on the trunk and, for every merged_not_recorded issue, either record it through plan verify|evidence|done with evidence actually run, or record why it is not done (a slice) by narrowing the issue or opening its remainder as a new issue; then make the drift gate blocking.
- Why
- ADR 0166, consequence 3. On 2026-10-16 at least I2653, I2417, I2652, I2734, I2601, I2288, I2289 and I2735 had merged pull requests naming them while not DONE; a blocking gate over them would turn the trunk red at once.
- Now
- Unknown count of merged but unrecorded issues on the trunk.
- Wanted
- plan drift on the trunk reports no merged_not_recorded, and the gate is blocking.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- plan drift on the trunk reports zero merged_not_recorded
- Every issue recorded DONE carries evidence from commands run at the recording commit
- Validation
bin/majordomus plan drift --jsonbin/majordomus plan validate- Evidence required
trunk_drift_zero- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.ai/repo/project/issues.ai/repo/ci/plan.yamldocs/PLAN_STATUS.mddocs/generatedsite/data/generatedsite/data/registry- Not
- unknown: the record declares no `non_scope`
- Depends on
- Priority
- p0
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-16
- Updated
- 2026-10-16
- 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.