All staff areas
Every area of the approved staff console, and whether this build has it.
Areas this build has
OverviewService, integration and data-mode state measured by this deployment.CustomersCustomer organizations, their members, seats, billing projection, audit, and the billing provider's webhook inbox.CatalogOpen a package, draft and edit a version, simulate what it grants, then validate, approve and publish it. Also the system workflow templates a customer project can be started from.DataLDG connection registry, capability coverage and the deployment's data mode.AI operationsProvider connections and their credential lifecycle, limit policies, live budget buckets and measured usage.SecurityStaff identities, permission groups, scopes, teams, access reviews, access diagnostics and audit.OperationsThe service, worker-queue and integration state this deployment measured about itself.CommunicationsThe delivery mode, sender, binding state, outcome histogram and backlog this deployment measured. Read-only: it operates nothing.ApprovalsDecide a change another operator requested. You can never decide your own.
Areas with no data behind them
Note: These open, and they hold nothing
Each row leads to the screen the specification declares, which states what the surface is for and names the exact operations that must be registered before it can show anything. None of them renders an empty table or a zero, because no data was read. They used to be inert text — a row that led to a 404 was worse than a row that led nowhere — and now there is somewhere honest for them to lead.
AI runs, routing and evaluationsaiRunCreate, aiRunGet and aiRunCancel answer 501 by owner decision, and routing policies, model/prompt configurations and evaluation suites are not registered at all. The AI operations area has a Runs screen that says exactly this rather than a table with nothing in it.Queues, incidents, feature flags, and acting on a job or a caseTwo of the concept's five Operations screens read something now: one job by its id (staffJobGet), and the support queue (staffSupportCasesList, at /support/cases). What is missing is the rest — staffJobsList, so there is no way to ask what is running; staffJobRetry and staffJobCancel, so a job is observed and never operated; every way of answering a support case; and every incident and feature-flag operation. The Operations area reports the worker and outbox state staffOverviewGet measures and names each of those.Communications managementEvery staffComm* operation — connections, credentials, message types, templates, journeys, broadcasts, delivery history and recovery, senders, reporting webhooks, suppressions, the platform pause and the sync ledger — is unregistered. The Communications area reads the measured delivery state and operates nothing.
Billing operations that change moneyReading is built: the provider projection on a customer account, the webhook inbox at Customers → Billing events, and one event's envelope. Replay, targeted reconciliation and refunds are registered addresses whose handlers refuse with capability_unavailable, so no control offers them.
Usage and revenue analytics (ADM-013)staffCommercialAnalytics and staffCommercialExportPreview are declared by the contract and unregistered. AI spending is measured and is on the AI operations usage screen; commercial revenue has no read path.Platform-wide audit searchAudit is readable scoped to one customer organization, and staff events have their own screen under Security. A platform-wide search by actor, capability, outcome or date across both has no read path.
Privacy requests, retention and compliance evidenceSEC-004, SEC-005 and SEC-006 have no registered operation in this build.Change feeds, replay and the data issue queueDAT-006's change feed and DAT-008's issue queue are unregistered. Serving manifests and derived-cache freshness ARE registered and are built, under Data.