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

I2406

The stream is documented where a reader looks

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
everything-is-followed-in-one-stream
Milestone status
ACTIVE
Wave
3
Waiting on
I2402I2404
Holds back
I2407
Behind it in all
1
Evidence
0 of 1
In the waySubjectDetail
issueI2402I2402 is not DONE
issueI2404I2404 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 I2406

majordomus plan verify I2406

majordomus plan done I2406

What it is

Objective
Write docs/MONITOR.md, a README section, cross-links from docs/MESH.md and docs/MCP.md, the site docs page through the generated copy, and a blog article written from what landed.
Why
An undocumented command is found by nobody but its author.
Now
Nothing documents it.
Wanted
The manual, README, site page and blog article describe it and link the ADR and the cases.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • docs/MONITOR.md documents every option and every signal kind
  • The site carries the docs page and the article and site-check passes
Validation
bin/majordomus plan validate
Evidence required
monitor_documented
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docsREADME.mdsite
Not
unknown: the record declares no `non_scope`
Depends on
I2402I2404
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-10-10
Updated
2026-10-10
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.