Skip to content

I1104 — Both namespaces carry their contracts, all the way down

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.

BLOCKED wave 2 · p1 · implementation profile · parallel safe

Part of two-folder-integration — A repository that adopts Majordomus gains two directories and two lines, and can give them back.

Blocked. This issue cannot start until I1102 is done. The status is derived from that, not declared.

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.

Current state

ADR 0011 established that every directory of the layer carries a contract, and a validator enforces it under `.ai/`. `.majordomus/` has no such requirement.

Desired state

The same validator covers both namespaces, and the effective context for an artifact composes from the contracts above it in either.

Scope

  • .majordomus

Out of scope

  • A second contract format for the second namespace
  • Duplicating a parent's instructions in every child

Dependencies

What waits on this

Acceptance criteria

  • 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 doctor
  • bash test/run.sh

Evidence required

  • contracts_present
  • composition_holds

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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.

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/I1104.yaml. Read it back with majordomus plan show I1104.