Skip to main content

capabilities

Function capabilities 

Source
async fn capabilities() -> Response
Expand description

GET /dashboard/api/capabilities

The dashboard’s own honesty ledger: what it can and cannot show, and why, so an operator does not have to infer completeness from an absent panel. plan/ops-dashboard.md’s “say what it cannot be trusted about” is not only this endpoint — the trust note on the page itself says the same thing in prose — but this is the machine-readable form of it. Public, like everything else this module serves: it names which epics are unbuilt and nothing else, which is a fact plan/ publishes anyway. Gating the honesty ledger behind the credential whose absence it is reporting was circular even before that credential turned out not to exist.

A live entry here carries data: null: this is the ledger, not the panel, and the number a panel has belongs on the panel. What the ledger says is which of the three states each panel is in and, for the ones that are not there, which epic each waits on.