I0927 — The cockpit shows the deployment from the same data

BLOCKED wave 3 · p2 · implementation profile · parallel safe

Part of fly-deployment — A deployment is a projection of the repository model, and a reachable URL is its evidence.

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.

Current state

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.

Desired state

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.

Scope

• apps/majordomus-cli/src/cockpit/pages.rs

Out of scope

• A second frontend, a second design language or a second data source
• Any credential reaching the browser
• Mutating deployment controls

Dependencies

• I0903BLOCKED Deployment reads are declared once and projected everywhere

What waits on this

• I0932BLOCKED The milestone is accepted on its evidence

Acceptance criteria

• 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-features
• bash test/run.sh

Evidence required

• cockpit_view
• data_from_model
• no_credentials_client

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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.

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/I0927.yaml. Read it back with majordomus plan show I0927.