I1007 — The site renders the same graph, generated once

READY wave 3 · p0 · implementation profile · parallel safe

Part of capability-graph — One capability graph, two projections, and no second inventory of what this repository can do.

Objective

Produce the static projection of the graph through the existing generation and site pipeline, so that the published site renders the same model the server does without a backend and without a second generator.

Why

A separate generation script for the site is the second universe this repository has already refused once. The generation target set exists and owns this.

Current state

The site is generated from the registry and several derived datasets by scripts that each know their own output.

Desired state

The static projection is a target of the canonical generation, and the site consumes it like its other derived data.

Scope

• apps/majordomus-cli/src/site.rs
• site

Out of scope

• A standalone cockpit generation script
• The static build requiring any runtime API to render

Dependencies

• I1005DONE The graph is a generated artifact with a schema and no unsafe field

What waits on this

• I1008BLOCKED The two projections are proved to be the same model
• I1013BLOCKED Search over the graph, generated, with nothing to run
• I1014BLOCKED The relation view reads the graph and holds no data of its own
• I1020BLOCKED The graph's health is answered by the doctor that already answers everything else
• I1022BLOCKED Drift in any derived surface fails the build

Acceptance criteria

• The static projection is produced by the canonical generation target set, with any shell involved being a thin adapter
• The published pages render the capabilities, the kinds, the relations and the coverage without any request to a backend
• Build-time and runtime data are distinguishable on the page, and a captured measurement is labelled as captured rather than shown as current
• The drift check covers the static projection

Validation

• majordomus generate --check
• bash test/run.sh

Evidence required

• static_projection
• no_backend_required

Evidence

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

Risk

Rendering yesterday's health as though it were current is the failure mode this issue exists to prevent, and it is a labelling problem, not a data problem.

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