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

I1123

The milestone is accepted on its evidence

Where it stands

devtask.issue
Readiness
blocked 8 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
8
Waiting on
I1104I1107I1115I1117I1118I1119I1120I1122
Holds back
none
Behind it in all
0
Evidence
0 of 3
In the waySubjectDetail
issueI1104I1104 is not DONE
issueI1107I1107 is not DONE
issueI1115I1115 is not DONE
issueI1117I1117 is not DONE
issueI1118I1118 is not DONE
issueI1119I1119 is not DONE
issueI1120I1120 is not DONE
issueI1122I1122 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 I1123

majordomus plan verify I1123

majordomus plan done I1123

What it is

Objective
Close the milestone: every acceptance criterion carries evidence, the measured baselines are recorded with the environment they were taken on, the adoption and removal run as documented on a clean checkout, and the remaining limitations are stated.
Why
A milestone is accepted by its evidence. What a later reader has is the record, not this session.
Now
Open.
Wanted
Accepted with evidence against every criterion, with the footprint, the budgets and the limitations written where they will be found.
Done when
unknown: the record declares no `completion`
Risk
The end of a long milestone is where intent gets recorded as outcome. Anything not demonstrated is written as a limitation.

Acceptance

  • Every acceptance criterion of the milestone has evidence recorded against it
  • The measured footprint of an adoption is recorded — every path, with its namespace and its owner
  • The budgets are recorded with the machine and environment they were measured on
  • The documented adoption and removal run exactly as written on a clean checkout
  • Pre-existing failures, failures introduced here and failures fixed here are distinguished explicitly
  • Remaining limitations are stated rather than omitted
Validation
bash test/run.shbin/majordomus doctormajordomus generate --check
Evidence required
criteria_coveredfootprint_recordedlimitations_stated
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docs/PLAN_STATUS.md.ai/repo/project
Not
Reporting a mechanism as proved without the artifact that proves it
Depends on
I1104I1107I1115I1117I1118I1119I1120I1122
Priority
p0
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-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.