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
I1507
Issues, milestones, sessions and peers reach the Cockpit as projections
Where it stands
devtask.issue- Readiness
- blocked 2 of its dependencies are not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
3- Waiting on
- Holds back
- none
- Behind it in all
0- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1505 | I1505 is not DONE |
| issue | I1506 | I1506 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Give the Cockpit the development areas it has none of — issues, milestones, sessions, peers and the current task — each one rendering what a capability answered and computing nothing of its own.
- Why
- Phase E of the audit's plan, and it is deliberately last. The gap matrix records issues and milestones as having no Cockpit page at all, and peers as reachable only through the generic runner despite peers.list and peers.announce both existing and both being covered by tests. Two capabilities landed after the audit's base that change the shape of this work: devtask.issue and devtask.milestone answer an issue and a milestone as work — readiness, waves, blockers, the parallel subsets, every value carrying whether a person authored it or a machine derived it — as a pure function of the canonical records, explicitly so that a work surface reading it derives nothing itself. That is the page's data source, already built. What must not happen is a page that computes a status: that is the defect the whole audit exists to prevent.
- Now
- No Cockpit page for issues, milestones, sessions or the current task. Peers have no area. devtask.issue and devtask.milestone are exposed on CLI, MCP and HTTP and on no page.
- Wanted
- Each area is a page that renders a capability's answer. A status shown on a page came from devtask or plan, and the page contains no rule for deriving one.
- Done when
- unknown: the record declares no `completion`
- Risk
- Medium. The tempting shortcut — a small status calculation in a template or in a browser module — is exactly the drift class the drift audit catalogued, including a browser module that already decides execution finality on its own.
Acceptance
- Each new area renders from a capability's answer with no status derived in the page or in the browser
- Every new page appears in the navigation and is reached by the probe
- A page shows everything it knows before any JavaScript loads
- Validation
bash test/run.shbin/majordomus-cli web- Evidence required
pages_are_projectionspages_are_navigable- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/cockpitshare/cockpitdocs/COCKPIT.mdtest/cases- Not
Any write path invented for a page. A page may only offer a transition that exists as a capability, through the mechanism the Cockpit already has.A second readiness vocabulary. devtask's refines the canonical statuses; a page must not add a third.- Depends on
- Priority
- p2
- 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-11
- Updated
- 2026-09-11
- 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.