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

I1104

Both namespaces carry their contracts, all the way down

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
2
Waiting on
I1102
Holds back
I1123
Behind it in all
1
Evidence
0 of 2
In the waySubjectDetail
issueI1102I1102 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 I1104

majordomus plan verify I1104

majordomus plan done I1104

What it is

Objective
Extend the directory-contract discipline that already governs `.ai/` to `.majordomus/`, so every directory of either namespace explains its purpose, its ownership, its lifecycle, the schemas that apply and how its contents are discovered.
Why
A control-plane directory nobody documented is where the next copy of something appears. The mechanism for preventing that already exists on one side of the boundary and simply does not run on the other.
Now
ADR 0011 established that every directory of the layer carries a contract, and a validator enforces it under `.ai/`. `.majordomus/` has no such requirement.
Wanted
The same validator covers both namespaces, and the effective context for an artifact composes from the contracts above it in either.
Done when
unknown: the record declares no `completion`
Risk
Mechanical coverage produces mechanical documents. A contract that says nothing a reader could not guess is a cost with no benefit, and the review has to say so.

Acceptance

  • Every directory of both namespaces carries a contract with valid typed front matter, and a missing one fails the existing validator
  • Each states purpose, ownership and lifecycle, the schemas that apply, and how its contents are discovered and extended
  • Contracts compose rather than repeat: a child adds to its ancestors and never restates them
  • The same mechanism serves both namespaces, with no second format
Validation
bin/majordomus doctorbash test/run.sh
Evidence required
contracts_presentcomposition_holds
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
.majordomus
Not
A second contract format for the second namespaceDuplicating a parent's instructions in every child
Depends on
I1102
Priority
p1
Profile
implementation
Parallel safe
true
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.