Operations

The Operations page is your situational-awareness view, and the console’s default landing page. It pulls fleet posture, control-plane health, the evidence pipeline, and current anomalies onto one screen. Glance here first, then drill into the page that needs you. Live host and session counts appear next to the page title.

Everything here is read-only. You can pause the evidence stream and continue to other pages, but nothing on this screen changes state.

The posture strip

A strip of cells across the top summarizes the tenant at a glance:

Cell	What it shows
Hosts	Total enrolled hosts, with connected and unknown counts beneath.
Posture	A stacked bar that splits the fleet by control-plane posture: active, isolated, lockdown, and stale. Beneath it, a fleet with nothing to answer for reads “n active” in one line; otherwise the stale, isolated, and lockdown counts are broken out. See Host posture.
Phi distribution	A stacked bar that splits the fleet by φ: healthy (φ < 8), warning (8 to 12), critical (12 and above), and unknown. See Fleet for how to read φ.
Lockdowns	How many lockdowns are in effect, plus how many enrollments are locked.
Governance queue	Change requests awaiting approval, plus how many already reached quorum. A change that reaches quorum leaves the awaiting count. Shows “Governance data unavailable” when the figures cannot load.
Server	Control-plane uptime.

When the Governance queue cell is non-zero, go to Approvals to review what is waiting.

The server card

The Churchill server card shows listener totals since the control plane started:

Active sessions: application sessions connected right now.
Conns rejected: connections the listener turned away. Tinted whenever it is above zero, because rejections usually mean something is misconfigured or unwelcome.
Kills sent: process-termination commands the control plane issued. Tinted whenever it is above zero. A non-zero value means enforcement fired, and you should understand why.

The full listener counters, including connections accepted, are on the server tab of Settings.

Evidence and recordings

The Evidence & recordings card tracks cumulative counters for the evidence pipeline:

Figure	Meaning
Received / Stored / Buffered	Evidence events received by the control plane, durably stored, and still buffered in flight.
Rejected batches	Evidence batches the control plane refused. Tinted when above zero. Investigate, because rejected evidence is evidence you do not have.
Invalid HMAC	Batches that failed authenticity verification. A non-zero value means something submitted evidence that could not prove where it came from.
Events lost	Events dropped because a store write failed.
Dropped batches	Batches dropped, with a breakdown beneath: `dup` (duplicate), `over` (oversized), and `mal` (malformed).
Recordings open / Complete	Session recordings being captured now, versus sealed and complete.
Rec bytes	Total recording data received.

Fleet flow

The Fleet flow card puts the fleet and its evidence pipeline on one board: a constellation of host nodes on the left, the control plane in the middle, and one branch per outcome on the right (stored, buffered, rejected, invalid HMAC, duplicate, lost). Each of the busiest hosts sends a band from its own node into the control plane at that host’s real events per second; the rest fold into a single band off the edge of the cluster. A failure branch takes an alert color the moment its rate leaves zero.

Each node encodes one host: its posture fills the node, its capture posture colors the ring around it, and a dashed ring means the host’s in-process sentinel is unarmed. Hover a node for the host’s name, φ and state, capture posture, inbound event rate, and host ID. Select it, or press Enter on it, to open that host’s detail page.

The card header counts the hosts, calls out how many are tampered or sentinel-unarmed, and states the fleet-wide inbound rate over the window it measured. With no hosts reporting it reads “No hosts reporting.”

Live evidence stream

The Live evidence stream card shows the most recent evidence events. It refreshes every few seconds while the indicator reads live. Each row carries the event time, host, event type, severity, decision, and reason.

Pause stops the refresh so you can read a row without it moving. Resume restarts the stream.
Select any row, or Open all →, to continue on the Evidence page with full filtering.

When there is nothing recent, the card shows “No evidence events in the loaded window”. If the stream cannot load at all, it shows “Evidence stream unavailable” with a short reason.

Anomalies

The Anomalies card lists every host in lockdown, critical, or warning, plus every host reporting a tampered capture posture. They are ordered worst first: lockdowns, then capture tampers, then critical, then warning, with hostname as the tie-break rather than φ, so the list does not reshuffle on every heartbeat. Each entry shows the host’s name, a short reason such as “lockdown active · φ 14.02”, “capture tampered · φ 3.10”, or “φ 9.10 elevated”, and the age of its last heartbeat. The Open host button opens that host’s detail page.

The card covers host telemetry only. It does not surface pending approvals or evidence spikes. Read it alongside the posture strip above.

When the fleet is clean, the card shows “No host anomalies.”

For the full sortable table view of the same fleet, use Fleet.