Skip to content

I1015 — A surface with no server behind it is not offered as if it had one

Make the exposure of backend-only surfaces — the API console, live status, runtime reads — follow from availability metadata, and prove both projections behave correctly.

ACTIVE wave 2 · 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

Make the exposure of backend-only surfaces — the API console, live status, runtime reads — follow from availability metadata, and prove both projections behave correctly.

Why

The published site has no server. A link to a runtime console on it is a broken promise, and the usual fix is a check on the page's own address, which is a rule hidden where nobody will find it.

Current state

The Swagger shell and the API are served by the running process. The published site has no way to know that.

Desired state

Exposure follows from availability metadata alone, and there is a test for each projection that keeps it that way.

Scope

  • apps/majordomus-cli/src/http/swagger.rs

Out of scope

  • Any decision made from a hostname, an address or a build flag inside a page
  • Rendering a dead destination as if it were live

Dependencies

What waits on this

Acceptance criteria

  • A backend-only surface is offered as usable only where a backend is available, decided from metadata
  • The static build contains no active link to a runtime-only surface
  • Where mentioning an unavailable surface is useful, it is shown as unavailable rather than omitted silently or linked
  • Both cases are tested — the static build and a running server with the API present

Validation

  • bash test/run.sh
  • scripts/cockpit-probe

Evidence required

  • availability_drives_exposure
  • both_projections_tested

Evidence

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

Risk

This is the check that quietly rots, because a broken link on a published page fails nothing. The test for it has to run on every build.

Timeline

started
2026-09-06T17:35:07Z
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/I1015.yaml. Read it back with majordomus plan show I1015.