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

I1006

The runtime reads the graph through the registry, like every other read

Where it stands

Readiness: complete completion is recorded and every required evidence token is present
Status: DONE
Can start: not now
Milestone: capability-graph
Milestone status: ACTIVE
Wave: 3
Waiting on: none
Holds back: I1008 I1017
Behind it in all: 3
Evidence: 2 of 2

Objective: Expose the graph to the running Cockpit as a declared capability, so that its route, its schema, its documentation and its benchmark coverage all follow from the declaration.
Why: A route added by hand for the Cockpit would be the one endpoint missing from OpenAPI, from the reference and from the smoke suite. The registry exists precisely so that does not happen.
Now: The Cockpit renders in-process. No capability serves the aggregate graph.
Wanted: One declared capability serves the graph, documented and benchmarked like the rest, with the runtime state layered over the definitions rather than mixed into them.
Done when: unknown: the record declares no `completion`
Risk: Serving the whole graph on every Cockpit load is a cost on the hot path. It is measured, and paged or filtered if the measurement says so.

The operation is one capability declaration and appears in the API, the OpenAPI document, the reference and the benchmark coverage without a second registration
The response is typed and carries safe fields only
Runtime state is an overlay over the definitions, distinguishable in the response
A test exercises the operation against a running server rather than a mock

Validation: cargo test --workspace --all-featuresmajordomus generate --check
Evidence required: capability_declaredruntime_overlay
Evidence present: capability_declaredruntime_overlay

Touches: apps/majordomus-cli/src/capability/builtin/graph.rs
Not: A route registered outside the capability registryRuntime state stored in the same structure as the definitions
Depends on: I1005
Priority: p1
Profile: implementation
Parallel safe: true
Owner: unknown: the record declares no `owner`

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

Nothing is wrong with these records.