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
I1028
The inventories this replaces are removed, not left running beside it
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
1- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1009 | I1009 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Find the hand-maintained inventories this architecture replaces — menus, landing cards, route lists, documentation indexes, rule and skill catalogues — and remove them, so that one derivation is the only one.
- Why
- Two systems doing the same job is worse than either alone: the old one keeps working just well enough that nobody notices it has diverged. Migration is finished when the thing it replaced is gone.
- Now
- Several surfaces assemble their own lists. Which ones exactly is a reconnaissance result, not an assumption.
- Wanted
- Each replaced inventory is deleted, its consumers read the derivation, and nothing hand-written survives as a fallback.
- Done when
- unknown: the record declares no `completion`
- Risk
- Removing a list that quietly held something the graph does not model loses content. Each removal is checked against what the derivation actually produces.
Acceptance
- The inventories that are replaced are enumerated from the repository, not assumed, and each is either removed or justified as authoritative for something else
- Every consumer reads the derivation after the removal
- Nothing that was removed is reachable as a fallback path
- The built site and the running interface show the same content as before the removal, except where the derivation is more complete
- Validation
bash test/run.shmajordomus generate --check- Evidence required
duplicates_removedconsumers_migrated- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
siteapps/majordomus-cli/src/cockpit/mod.rs- Not
Deleting a list that is genuinely authoritative for something the graph does not modelLeaving a hand-written list in place as a fallback- Depends on
- Priority
- p1
- Profile
- deep-work
- 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-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.