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
I1017
Live state is an overlay that degrades to nothing
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
4- Waiting on
- none
- Holds back
- Behind it in all
1- Evidence
0of2
Moves
plan.transitionWhat it is
- Objective
- Let the running Cockpit overlay live state — health, peers, runtime metrics, deployment status — over the same graph, through the transport the process already has, degrading cleanly where there is none.
- Why
- Live state is what makes a control plane worth opening. It is also what makes a static page lie, so it has to be an overlay that is visibly absent rather than a field that is silently stale.
- Now
- The process has a health capability and peers. No surface subscribes to anything.
- Wanted
- Live values arrive over the existing transport, are visibly distinct from the snapshot, and are absent rather than stale where no backend answers.
- Done when
- unknown: the record declares no `completion`
- Risk
- Live overlays are where credentials leak into browsers. Everything sent to the client is an allowlisted safe field.
Acceptance
- Live updates use the process's existing event transport rather than a new one
- Live values are visually and structurally distinguishable from snapshot values
- The static projection renders the useful equivalent — what the endpoint is, and that the value is available when a server runs — rather than an empty card
- Reconnection is bounded and backs off, and a failed connection does not produce a request storm
- Validation
scripts/cockpit-probecargo test --workspace --all-features- Evidence required
overlay_livedegrades_cleanly- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/cockpit/html.rs- Not
A transport invented for the Cockpit alongside one that already existsA reconnect loop with no bound- Depends on
- Priority
- p2
- Profile
- implementation
- Parallel safe
- true
- 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.