Skip to content

I1118 — Every invariant of this milestone is a rule with a check that runs

Turn the invariants — bounded footprint, no manual registration, disposable derived artifacts, reversible managed mutations, idempotent reconciliation, root files as adapters, zero-registration extension — into project rules, each with an executable check that CI runs and a negative test that proves it fires.

BLOCKED wave 7 · p0 · deep-work 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 I1110, I1116 are done. The status is derived from that, not declared.

Objective

Turn the invariants — bounded footprint, no manual registration, disposable derived artifacts, reversible managed mutations, idempotent reconciliation, root files as adapters, zero-registration extension — into project rules, each with an executable check that CI runs and a negative test that proves it fires.

Why

Everything in this milestone decays the moment a change can land without a check noticing. A rule with no check is a suggestion, and this repository has a rule saying exactly that.

Current state

The invariants exist as prose in the mission and as behaviour in the code. No rule states them and no check enforces them.

Desired state

Each invariant is a rule with a check, each check has a negative test, and CI runs all of them.

Scope

  • .ai/repo/rules/project

Out of scope

  • A rule with no executable check
  • Restating a constraint an existing rule already enforces

Dependencies

What waits on this

Acceptance criteria

  • Majordomus-owned persistent state outside the two namespaces fails a check unless the ledger records it as a bridge
  • A secondary registry enumerating a discoverable namespace fails a check
  • A generated artifact without provenance, or read back as canonical input, fails a check
  • A mutation outside the two namespaces without a ledger entry fails a check
  • A non-idempotent reconciliation fails a check
  • Each rule has a negative test proving its check fires, and CI executes every one

Validation

  • bin/majordomus doctor
  • bash test/run.sh

Evidence required

  • rules_authored
  • checks_fire
  • ci_runs_them

Evidence

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

Risk

Seven rules for one milestone is a lot of doctrine. Any constraint an existing rule already covers is referenced rather than restated, and the review has to insist on that.

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