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

I0843

The performance workflow is discoverable and complete

Where it stands

devtask.issue
Readiness
blocked 4 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
M004
Milestone status
ACTIVE
Wave
6
Waiting on
I0831I0835I0841I0842
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI0831I0831 is not DONE
issueI0835I0835 is not DONE
issueI0841I0841 is not DONE
issueI0842I0842 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 I0843

majordomus plan verify I0843

majordomus plan done I0843

What it is

Objective
Close the milestone: every acceptance criterion of M004 has evidence, the README workflow runs as written, the site is regenerated, and the final report is a plan record rather than a conversation.
Why
A milestone is accepted by its evidence, not by finishing its issues.
Now
Open.
Wanted
M004 accepted with evidence on every criterion.
Done when
unknown: the record declares no `completion`
Risk
The last issue is the one that checks the others honestly.

Acceptance

  • plan validate passes and M004 reports every evidence_required token satisfied
Validation
bin/majordomus plan validatebin/majordomus plan status
Evidence required
docs_integrated
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docs/PLAN_STATUS.md.ai/repo/project
Not
none
Depends on
I0830I0831I0835I0841I0842
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-05
Updated
2026-09-05
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.