I2406 — The stream is documented where a reader looks
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.
BLOCKED wave 3 · p2 · implementation profile · runs alone
Blocked. This issue cannot start until I2402, I2404 are done. The status is derived from that, not declared.
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.
Current state
Nothing documents it.
Desired state
The manual, README, site page and blog article describe it and link the ADR and the cases.
Scope
- docs
- README.md
- site
Dependencies
- I2402READY majordomus monitor follows the stream from a terminal and a script
- I2404READY The Cockpit shows the stream live
What waits on this
Acceptance criteria
- 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
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2406.yaml. Read it back with majordomus plan show I2406.