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

I0932

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
fly-deployment
Milestone status
ACTIVE
Wave
9
Waiting on
I0920I0923I0925I0926I0927I0928I0929I0931
Holds back
none
Behind it in all
0
Evidence
0 of 3
In the waySubjectDetail
issueI0920I0920 is not DONE
issueI0923I0923 is not DONE
issueI0925I0925 is not DONE
issueI0926I0926 is not DONE
issueI0927I0927 is not DONE
issueI0928I0928 is not DONE
issueI0929I0929 is not DONE
issueI0931I0931 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 I0932

majordomus plan verify I0932

majordomus plan done I0932

What it is

Objective
Close the milestone: every acceptance criterion carries evidence, the measured baselines are documented with the environment they were taken on, the workflow in the documentation runs as written, and the outcome is a plan record rather than a conversation.
Why
A milestone is accepted by its evidence. The numbers, the commands and the deployed URL are what a later reader has; this session's messages are not.
Now
Open.
Wanted
The milestone is accepted with evidence against every criterion, and the baselines and limitations are written where they will be found.
Done when
unknown: the record declares no `completion`
Risk
The temptation at the end is to record intent as outcome. Anything not demonstrated is a limitation, and it is written as one.

Acceptance

  • Every acceptance criterion of the milestone has evidence recorded against it
  • The measured baselines — binary, image, context, build durations, readiness, resident memory, endpoint latency — are documented with the machine and environment they were measured on
  • The developer workflow in the documentation runs 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 deploy doctor
Evidence required
baselines_documentedcriteria_coveredreport_recorded
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docs/PLAN_STATUS.md.ai/repo/project
Not
Reporting a plan as an implementationRecording a measurement without the environment it was taken on
Depends on
I0920I0923I0925I0926I0927I0928I0929I0931
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.