AI operations console — every capability slot on the platform, watched live
14slots watched
0running
11idle
0no model
3open alerts
1inferences
INTACTaudit chain · 2 events
Performance computed from the Data Store and the audit
trail — never self-reported by a model. Each station below leads with the
same reading its documentation shows, so the console and the reference
cannot drift apart. Idle is a state, not a gap: a slot with
no invocations is watched and shown as idle, and a slot with no model at all
is shown as unstaffed rather than omitted.
8 billed claims have no supporting note in their window - a compliance backlog, not just a finding count.
Acknowledging is audited under your name. A condition that
recurs after acknowledgment re-fires — alerts never auto-close, and nothing
here can be dismissed without leaving a trace.
The same dashboards the model
documentation renders, gathered here in one console. Open the ones you are
watching; the rest stay closed so the panel keeps its shape.
Signals that belong to no single
model. Refusals are a health reading, not an error log: a
system that never refuses anything is either not being asked hard questions
or is not checking. The scope tripwire is the exception — it should read
zero, and any other number is a defect.
0
Role / permission denied
a request outside the signed-in role
access.denied
0
Retrieval withheld
sensitivity fence held a record back from the assistant
retrieval.withheld
0
Release refused
requirements unmet, with the rule named
roi.refused
0
Bulk export refused
consent or scope failed at the door
bulk.refused
0
Scope violation caught
context tripwire - should read zero
system.scope_violation
What monitoring cannot do. These instruments watch the
models; they do not validate them clinically, and they do not discharge the
organization's AI-oversight duties. Local validation before clinical use,
subgroup review on the fairness screen, and the authority to pull the
switches remain human responsibilities. A green console is evidence that
the thresholds held — not that the model is right.
This public demo records how it is used, so it can be made better:
a required session cookie that keeps your sandbox yours, first-party usage
analytics — including the questions put to the assistant — held in our own
database, and optional Google Analytics. Google never receives anything you
type. Every patient here is synthetic, so nothing you read is anyone's
health information.