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
I0927
The cockpit shows the deployment from the same data
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
3- Waiting on
- none
- Holds back
- Behind it in all
1- Evidence
0of3
Moves
plan.transitionWhat it is
- Objective
- Add a deployment view to the existing cockpit that reads static policy from the canonical object and live facts from the running process, using the projection the cockpit already is.
- Why
- The cockpit exists to project what the registry knows. A deployment that is invisible there is a subsystem outside the model, and a deployment view fed by its own data source would be a second inventory.
- Now
- The cockpit renders pages, navigation and views derived from the registry and the index, under ADR 0012, and is under active development on another branch.
- Wanted
- One view shows the provider, the application, the deployed revision, the region, the machine, the runtime profile and the health, drawing static facts from the canonical object and live facts from the metadata read.
- Done when
- unknown: the record declares no `completion`
- Risk
- The cockpit is being rebuilt on another branch. This view has to be written against its projection model rather than against its current markup, and landed after it.
Acceptance
- Static deployment policy comes from the canonical object and live facts from the same metadata read the API serves
- No credential of any kind reaches the client, and a test proves it
- The view carries no mutating control
- The view appears through the cockpit's existing navigation derivation rather than a hardcoded entry
- Absent live data renders as absent rather than as a broken or empty card
- Validation
cargo test --workspace --all-featuresbash test/run.sh- Evidence required
cockpit_viewdata_from_modelno_credentials_client- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/cockpit/pages.rs- Not
A second frontend, a second design language or a second data sourceAny credential reaching the browserMutating deployment controls- 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
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | scope_conflict | shares apps/majordomus-cli/src/cockpit/pages.rs with I1010; they may not run concurrently | majordomus plan validate |