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

I1118

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

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
7
Waiting on
I1110I1116
Holds back
I1123
Behind it in all
1
Evidence
0 of 3
In the waySubjectDetail
issueI1110I1110 is not DONE
issueI1116I1116 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 I1118

majordomus plan verify I1118

majordomus plan done I1118

What it is

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.
Now
The invariants exist as prose in the mission and as behaviour in the code. No rule states them and no check enforces them.
Wanted
Each invariant is a rule with a check, each check has a negative test, and CI runs all of them.
Done when
unknown: the record declares no `completion`
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.

Acceptance

  • 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 doctorbash test/run.sh
Evidence required
rules_authoredchecks_fireci_runs_them
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
.ai/repo/rules/project
Not
A rule with no executable checkRestating a constraint an existing rule already enforces
Depends on
I1110I1116
Priority
p0
Profile
deep-work
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.