---
term: service dashboard
category: service-runtime
status: canonical
authority: conductor.elonn.local
---

Service Dashboard

An Object that provides an operable interface to one Service, built generically from that
Service's own published Contract — not hand-written per Service. A Service Dashboard exists once
per approved Service; it is not a single global member home screen.

Allowed:
- service dashboard
- open the [service] dashboard
- dashboard action

Forbidden:
- the member dashboard (there is no single global dashboard; see: workspace)
- dashboard (bare, ambiguous — always qualify as "service dashboard")
- global service launcher

Notes:
- Conductor is the authority for Service Dashboard content: it reads a Service's approved
Publication and cached Contract and emits the Dashboard Object generically, the same way it
already attaches Contract argument schemas to any Dataset action via ActionArgumentEnricher.
World composes a Service Dashboard into the runtime contract but does not own it — the same
relationship World has to field content, which Maps owns.
- A Service Dashboard's actions come from that Service's declared entrypoints (see: contract) —
its own meaningful, standalone human entrances, independent of model_selectable. A Contract
that has not declared entrypoints falls back to its model_selectable: true operations, so a
Service is never left without a Dashboard while it hasn't yet adopted the concept.
- A Service Dashboard is placed on Carry (a carry Placement — see
[layout.md](../canonical/layout.md), Dashboard, and placement.md). Its entry points are
actionable: focusing one may open an Object on Carry, or open another Dashboard on Carry.
How a runtime presents it — as a panel or a window — is presentation, not placement.
- Distinct from the legacy, Android/iPad/Cardboard-only dashboard_surface Surface type (see:
surface) — that concept predates and is unrelated to this one.

Related:
- carry
- object (runtime term)
- action
- contract
- conductor