I1101 — What this tool leaves behind, established by inspection rather than by memory
Establish, from the repository rather than from recollection, every path Majordomus writes, generates or mutates when a project adopts it — where each lands, which subsystem writes it, whether anything records it, and which are canonical, derived or accidental.
READY wave 0 · p0 · deep-work profile · parallel safe
Ready. Every dependency is done, so majordomus plan start I1101 will be accepted.
Objective
Establish, from the repository rather than from recollection, every path Majordomus writes, generates or mutates when a project adopts it — where each lands, which subsystem writes it, whether anything records it, and which are canonical, derived or accidental.
Why
The two-folder contract is a claim about a footprint nobody has measured. Every later phase — the layout, the reconciler, the ledger, the migration — is a decision about paths, and a decision about paths made from memory will be wrong in the way that only shows up in a foreign repository.
Current state
`.ai/` and `.majordomus/` both exist. Provider bootstraps are generated to the root, root documents carry generated blocks, and no inventory says what else a subsystem writes or under what circumstances.
Desired state
One document records the actual footprint with its writer, its lifecycle and its justification, and names which of them the target architecture keeps, moves or removes.
Scope
- docs/INTEGRATION.md
- .ai/repo/adrs
Out of scope
- Moving anything; this issue changes no path
- A rewrite of a subsystem discovered along the way
Dependencies
None. This issue is a root of the graph.
What waits on this
- I1102BLOCKED The two namespaces are a typed contract, not a habit
- I1105BLOCKED The repository is discovered once, into one model
Acceptance criteria
- Every path written or mutated outside `.ai/` and `.majordomus/` is listed with the code that writes it, found by inspection rather than by assumption
- Each is classified as canonical, derived, generated, cache, runtime or accidental, with the reason
- The classification says which paths the two-folder contract keeps as bridges, which move into a namespace and which stop existing
- Where an existing mechanism already does what a later phase would add, it is named so the phase extends it rather than replacing it
- The architectural decision is recorded in the repository's own ADR mechanism, not in prose beside it
Validation
- bin/majordomus doctor
- bash test/run.sh
Evidence required
- footprint_inventory
- decision_recorded
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Risk
A forensic phase can become a rewrite the moment it finds something ugly. It records; the phases that follow change.
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/I1101.yaml. Read it back with majordomus plan show I1101.