Skip to content
Cockpit0.29.0
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

I1117

The hand-maintained lists are removed, not left running beside the derivation

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
3
Waiting on
I1106
Holds back
I1123
Behind it in all
1
Evidence
0 of 2
In the waySubjectDetail
issueI1106I1106 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1117

majordomus plan verify I1117

majordomus plan done I1117

What it is

Objective
Find every list that enumerates what discovery already finds — indexes, menus, route tables, provider lists, documentation catalogues — and remove it, 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. This session alone found the same route list four times and a page list twice.
Now
Several such lists have been removed already; the rest are what phase one recorded and what the derivation makes redundant.
Wanted
Each replaced list is deleted, its consumers read the derivation, and nothing survives as a fallback.
Done when
unknown: the record declares no `completion`
Risk
A list quietly holding something the model does not carry loses that content when it goes. Each removal is checked against what the derivation actually produces, item by item.

Acceptance

  • The lists that are replaced are enumerated from the repository rather than assumed, and each is removed or justified as authoritative for something else
  • Every consumer reads the derivation after the removal, and nothing removed remains reachable as a fallback
  • What the interfaces show is the same as before the removal, except where the derivation is more complete
  • A check refuses a new enumeration of a discoverable namespace
Validation
bash test/run.shmajordomus generate --check
Evidence required
duplicates_removedenumeration_refused
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/srcsite
Not
Deleting a list that is genuinely authoritative for something the model does not holdLeaving a hand-written list in place as a fallback
Depends on
I1106
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.