spacedb-console — the operator's read-model
The substance of an operations console is not pixels — it is the logic that
turns raw fleet / access / audit / settlement [Observations] into the four
boards a SpaceDB business is run from:
- Fleet Health ([
FleetHealth]) — durability + availability: under-replicated, at-risk and lost shards, quorum loss, lag; one Green/Amber/Red rollup. - Access & Audit ([
AccessOverview]) — human vs AI-agent capabilities, expirations, revocations, per-agent activity, denials. - Economics ([
Economics]) — revenue, spend per customer, per-rail split, agent budget burn-down, unsettled claims. - Alerts ([
Alert]) — the page-me surface, severity-sorted.
[Dashboard::assemble] computes all four from one snapshot; [Dashboard::render_text]
prints them. A Dioxus/WASM shell binds the same fields to a UI:
// in the Dioxus shell (compiles to wasm32, not part of the tested core):
let dash = Dashboard::assemble(&observations, &Config::at(now));
rsx! {
HealthBadge { status: dash.health.status }
for alert in dash.alerts { AlertRow { alert } }
EconomicsPanel { economics: dash.economics }
}
Open-core (MIT). Fed by observation DTOs, so it stays decoupled and testable.