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

I1116

This repository's own footprint moves, through the reconciler

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
6
Waiting on
I1110I1112
Holds back
I1118I1122
Behind it in all
3
Evidence
0 of 3
In the waySubjectDetail
issueI1110I1110 is not DONE
issueI1112I1112 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 I1116

majordomus plan verify I1116

majordomus plan done I1116

What it is

Objective
Migrate what this repository itself scatters — root scripts, provider files, configuration beside configuration, generated state outside the namespaces — into `.ai/` and `.majordomus/`, using the reconciler and its migrations rather than a move script.
Why
The tool has to survive its own contract. A repository that ships a two-folder promise while keeping a root full of exceptions is the least convincing possible demonstration, and it is also where every latent assumption about paths will surface.
Now
The footprint is what phase one recorded. Nothing has moved.
Wanted
The repository conforms to its own contract, every move is recorded, and nothing that was working stopped working.
Done when
unknown: the record declares no `completion`
Risk
This is the phase where the tool is changed by the thing it is changing, with several sessions working in the same repository. It runs once, as a dry run first, and not concurrently with other structural work.

Acceptance

  • Every move goes through a recorded migration, previewable as a dry run before it is applied
  • Compatibility is preserved for the paths other work depends on, or the break is deliberate, documented and migrated
  • After the migration this repository conforms to its own contract, checked by the same validator a foreign repository would face
  • Nothing that was working before stops working, proved by the full suite rather than by inspection
Validation
bash test/run.shbin/majordomus doctormajordomus generate --check
Evidence required
footprint_migratedconformance_selfnothing_broke
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
scripts.majordomus
Not
A broad recursive delete anywhereMoving user-authored content without recording where it wentA shell script that performs the migration outside the reconciler
Depends on
I1110I1112
Priority
p0
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.