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
I0603
Report drift from the shared policy in one command
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
2- Waiting on
- Holds back
- Behind it in all
2- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I0602 | I0602 is not DONE |
| milestone | shared-policy | the milestone shared-policy waits on an outcome of its own |
Moves
plan.transitionWhat it is
- Objective
- Report, in one command, every way a repository's effective policy differs from the shared source it names, separating declared overrides from undeclared divergence.
- Why
- The point of naming a shared source is being able to see where it is not being followed. Without one command that answers that, shared policy is just a longer path to the same drift.
- Now
- A shared source is resolved and overrides are declared. Nothing summarises the difference.
- Wanted
- One command lists each difference, says whether it is a declared override or undeclared divergence, and names the reproduce command for each.
- Done when
- unknown: the record declares no `completion`
- Risk
- A drift report that is noisy is a drift report nobody runs; declared overrides have to be quiet by default.
Acceptance
- Every difference is listed with the key, both values, and whether it is declared
- Undeclared divergence exits non-zero and declared overrides do not
- Every finding carries a reproduce command
- The command writes nothing
- Validation
bash test/run.sh- Evidence required
suite- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
libbin- Not
Changing anybody's policy; the command reports and never writes- Depends on
- Priority
- p3
- 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-09-04
- Updated
- 2026-09-04
- 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.