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

I1101

What this tool leaves behind, established by inspection rather than by memory

Where it stands

Readiness: review implementation is declared finished and completion is not recorded
Status: VERIFY
Can start: not now
Milestone: two-folder-integration
Milestone status: ACTIVE
Wave: 0
Waiting on: none
Holds back: I1102 I1105
Behind it in all: 22
Evidence: 2 of 2

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.
Now: `.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.
Wanted: 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.
Done when: unknown: the record declares no `completion`
Risk: A forensic phase can become a rewrite the moment it finds something ugly. It records; the phases that follow change.

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

Touches: docs/TWO_FOLDER_CONSOLIDATION.md.ai/repo/adrs
Not: Moving anything; this issue changes no pathA rewrite of a subsystem discovered along the way
Depends on: none
Priority: p0
Profile: deep-work
Parallel safe: true
Owner: unknown: the record declares no `owner`

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

Nothing is wrong with these records.