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

I1309

The boundaries this milestone asserts are gates, not sentences

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
external-workspaces
Milestone status
ACTIVE
Wave
4
Waiting on
I1303I1308
Holds back
I1310
Behind it in all
1
Evidence
0 of 5
In the waySubjectDetail
issueI1303I1303 is not DONE
issueI1308I1308 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 I1309

majordomus plan verify I1309

majordomus plan done I1309

What it is

Objective
Add the gates that make ADR 0025 enforceable: the dependency boundary of majordomus-cli, the credential leak check over the store and the fixtures, the retention cap, and the publication boundary.
Why
This repository's own doctrine is that a rule enforced by nobody is normative for whoever reads it and nothing else. Three of the four boundaries here are exactly the kind that hold until the first hurried afternoon.
Now
No gate covers any of them. The only adjacent precedent is scripts/site-check, which greps rendered output for secret-shaped strings and fails the site gate.
Wanted
Four gates in .ai/repo/ci/gates.yaml, each a script, each selected by the paths it protects, each with a test case that proves it fails when the boundary is crossed.
Done when
unknown: the record declares no `completion`
Risk
A leak grep tuned to today's token shapes finds today's tokens. It is a floor, and the record says so rather than implying the boundary is proven.

Acceptance

  • A gate fails if majordomus-cli's runtime dependency list changes, naming what was added
  • A gate greps the store, the fixtures, the logs and the snapshots for credential-shaped values and fails on a hit
  • A gate fails if the store exceeds its declared retention cap
  • A gate fails if any published projection names a path under .ai/local/workspaces/
  • Each gate has a test case that proves it red before it proves it green, and each rule carries the x-majordomus block that makes it enforced rather than stated
Validation
bash test/run.shscripts/ci-plan --fullbin/majordomus doctrine
Evidence required
dependency_gatedleak_gatedretention_gatedpublication_gatedeach_gate_proven_red
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
.ai/repo/ci/gates.yaml.ai/repo/rules/projectscripts/citest/casesdocs/CLAIMS.yaml
Not
Adding a new CI job; these gates belong to jobs that already exist
Depends on
I1303I1308
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-09
Updated
2026-09-09
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.