I1116 — This repository's own footprint moves, through the reconciler
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.
BLOCKED wave 6 · p0 · deep-work profile · runs alone
Blocked. This issue cannot start until I1110, I1112 are done. The status is derived from that, not declared.
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.
Current state
The footprint is what phase one recorded. Nothing has moved.
Desired state
The repository conforms to its own contract, every move is recorded, and nothing that was working stopped working.
Scope
- scripts
- .majordomus
Out of scope
- A broad recursive delete anywhere
- Moving user-authored content without recording where it went
- A shell script that performs the migration outside the reconciler
Dependencies
- I1110BLOCKED The second run changes nothing, and a test says so
- I1112BLOCKED What touches the root is two small blocks, and they never change again
What waits on this
- I1118BLOCKED Every invariant of this milestone is a rule with a check that runs
- I1122BLOCKED A foreign repository, adopted, upgraded and given back
Acceptance criteria
- 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.sh
- bin/majordomus doctor
- majordomus generate --check
Evidence required
- footprint_migrated
- conformance_self
- nothing_broke
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
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.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I1116.yaml. Read it back with majordomus plan show I1116.