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

I0203

Make enforcement opt-in, and prove a repository that declines is unaffected

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
runtime-adapters
Milestone status
PLANNED
Wave
2
Waiting on
I0202
Holds back
I0204
Behind it in all
3
Evidence
0 of 1
In the waySubjectDetail
issueI0202I0202 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 I0203

majordomus plan verify I0203

majordomus plan done I0203

What it is

Objective
Add one policy key that turns runtime enforcement on, default it to off, and prove with a case that a repository which never sets it behaves exactly as it does today.
Why
Clamping what a worker may read or emit changes how every session behaves. A change of that size cannot arrive with an update; it has to be chosen, and the choice has to be visible in the policy the repository already reviews.
Now
Nothing is enforced, so nothing needs an opt-in. Adding the adapter without one would enforce limits in every repository that updates.
Wanted
The policy carries an explicit enforcement key. Absent or false, the tool behaves as it did before the adapter existed, and a case demonstrates that rather than asserting it.
Done when
unknown: the record declares no `completion`
Risk
An opt-in that defaults to on in the skeleton is not an opt-in; the skeleton has to be covered by the same case.

Acceptance

  • The key is declared in the policy allowlist and rejected when it holds anything but a boolean
  • Default and absent both mean off, and the projections say so where a worker reads them
  • A case runs the full lifecycle in a repository that never sets the key and shows unchanged behaviour
  • Doctor reports whether enforcement is on, without turning it on
Validation
bash test/run.shbin/majordomus doctor
Evidence required
suite
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
libshare
Not
Any default that enables enforcementPer-command overrides; the choice is the repository's, once
Depends on
I0202
Priority
p1
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-04
Updated
2026-09-04
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.