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
I0602
Make a local override explicit and prove it survives an update of the shared source
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
1- Waiting on
- Holds back
- Behind it in all
3- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I0601 | I0601 is not DONE |
| milestone | shared-policy | the milestone shared-policy waits on an outcome of its own |
Moves
plan.transitionWhat it is
- Objective
- Define how a repository overrides part of a shared policy, require the override to be declared rather than inferred from a value differing, and prove with a case that updating the shared source leaves the override standing.
- Why
- An override that looks like an ordinary key is indistinguishable from a stale copy. Declaring it is what lets the drift report tell a deliberate exception from an accident.
- Now
- A shared source can be named and resolved. Anything a repository writes locally either wins or loses by a rule nobody has written down.
- Wanted
- Overrides are declared, the merge order is documented and tested, and a shared source that changes underneath a repository does not silently take an override away.
- Done when
- unknown: the record declares no `completion`
- Risk
- Merge semantics are where shared configuration usually becomes unexplainable; the documented order and its case are the whole defence.
Acceptance
- An override is a declaration, and a local value that differs without one is a finding
- The merge order is documented and covered by a case
- A case updates the shared source and shows the override still applies
- Validation
bash test/run.sh- Evidence required
suite- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
libsharedocs- Not
Overriding a rule the shared policy declares non-overridable, if such a class is introduced later- 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.