SENTINEL COMMANDOperating layer

Every system, one operating view.

SEE. UNDERSTAND. AUTHORIZE. ACT. VERIFY.

Sentinel Command connects every system into one operational view. It is where a person sees the state of the estate and of Sentinel itself, understands it, authorizes a response, acts, and verifies the result.

A dark command room. An operator sits before three crimson traces. A gloved hand rests on a gold key.
Place on the operating loopSUPERVISES THE ENTIRE LOOP
  1. 01ObserveContinuous telemetry from every AXIS service and edge. (Command spans this stage)
  2. 02VerifyTelemetry checked at the gateway before it is trusted. (Command spans this stage)
  3. 03DetectAnomaly, policy violation, and absent signal alike. (Command spans this stage)
  4. 04ProtectPolicy enforced at the identity and tenant boundary. (Command spans this stage)
  5. 05PreserveEvidence written down before it can be lost. (Command spans this stage)
  6. 06RecoverContinuity coordinated, state restored, result verified. (Command spans this stage)

Recover returns to Observe

Command is where a person supervises every stage of the loop.

The operating picture

One view. Every system, each with its own state.

This is the Command demonstration's own surface, built from the same scenario. Step through it: detection, enforcement, preservation and a verified recovery.

Illustrative demonstration, fabricated data
Operational stateNominal

All sources reporting. Gateway checks passed.

Every AXIS service and the Cloudflare edge are emitting SCEF telemetry on schedule. Sentinel is indexing events and holding the evidence chain. Nothing is open.

AXIS 7DserviceverifiedAXIS COREserviceverifiedAXIS OMNIAserviceverifiedCLOUDFLARE EDGEedgeverifiedSENTINELcontrol planeverifiedD1 INDEXevent indexreportingEVIDENCE STOREraw evidencereportingCOLOSSEUMcontinuityreporting
  • COLOSSEUMcontinuityReporting
  • D1 INDEXevent indexReporting
  • EVIDENCE STOREraw evidenceReporting
  • AXIS 7DserviceVerified
  • AXIS COREserviceVerified
  • AXIS OMNIAserviceVerified
  • CLOUDFLARE EDGEedgeVerified
  • SENTINELcontrol planeVerified

Event stream

  • Earlierinfo
    AXIS-OMNIAWorkspace Birch

    INDEX_COMMIT

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-ELM
  • Earlierinfo
    CLOUDFLARE-EDGE—

    EDGE_POLICY_APPLIED

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-LARCH
  • Earlierinfo
    AXIS-COREWorkspace Alder

    TELEMETRY_HEARTBEAT

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-FERN

Simulated scenario on fabricated data. Every identifier, tenant and trace here is invented.

Command, operating pictureThe topology, Watchtower coverage, response posture and event stream, each step drawn from one scenario. Every identifier, tenant and trace is invented.

The supervision cycle

See. Understand. Authorize. Act. Verify.

Command decides nothing on its own authority. It puts a person in front of every system's state, and sends a decision back out only under that person's recorded authority.

A wide view of the control hall as the camera draws toward one stream. The operating surface is dimmed around a single amber marker on the Guard node, ringed and glowing, with the seven streams still running in along the mirror floor.
01AttentionOne stream asks to be looked at. The picture draws toward it and dims the rest.
The same view with a person's authority light lit: the proposed-response panel on the operating surface is framed by a champagne hairline, and the amber marker is held beside it. A person's authority light is on; the picture proposes and waits.
02DecideA person's authority light is on. Command proposes; the person decides.
The operating surface as a platinum check-light passes across it. The amber marker has settled to champagne, the authority frame is dimmed, and the streams run steadily into the glass.
03VerifyA platinum check-light passes over the picture. Only a verified result settles the marker.
  1. See

    Watchtower reports a deployment as degraded and Guard reports a session it challenged. Both arrive in one view, each with its own state.

  2. Understand

    Trace places the two findings in sequence. Each record says how it is known: Watchtower's finding is server observed, the session report is site reported.

  3. Authorize

    Command offers only the responses the operator's role allows. The server re-validates the role, the tenant, the legal transition and the Safe Mode scope before anything happens.

  4. Act

    The operator contains the session and requests preservation. Guard enforces the containment, and the Ledger records both actions with the authority each used.

  5. Verify

    Watchtower confirms the deployment is reporting again and the recovery-verification task is complete. Only then does the server accept the incident's close.

Incident to recovery

From a declared incident to a verified restore point.

The same surface, the last four steps of the scenario: the incident, Safe Mode, COLOSSEUM preserving state, and the verified recovery. COLOSSEUM is a separate system; there is no live COLOSSEUM integration.

Illustrative demonstration, fabricated data
Operational stateInvestigating

An incident is declared.

A commander declares the incident. The timeline now carries every correlated signal, the enforcement action and the sealed evidence reference — assembled as it happened rather than reconstructed afterwards.

AXIS 7DservicedegradedAXIS COREserviceverifiedAXIS OMNIAserviceno signalCLOUDFLARE EDGEedgeverifiedSENTINELcontrol planeverifiedD1 INDEXevent indexreportingEVIDENCE STOREraw evidencereportingCOLOSSEUMcontinuityreporting
  • AXIS OMNIAserviceNo signal
  • AXIS 7DserviceDegraded
  • COLOSSEUMcontinuityReporting
  • D1 INDEXevent indexReporting
  • EVIDENCE STOREraw evidenceReporting
  • AXIS COREserviceVerified
  • CLOUDFLARE EDGEedgeVerified
  • SENTINELcontrol planeVerified

Event stream

  • Just nowhigh
    AXIS-7DWorkspace Cedar

    PRIVILEGED_SESSION_CREATED

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-ORCHID
  • Just nowmedium
    SENTINELWorkspace Cedar

    TRACE_ASSEMBLED

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-ORCHID
  • Just nowmedium
    CLOUDFLARE-EDGEWorkspace Cedar

    REQUEST_CORRELATED

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-ORCHID
  • Shortly aftercritical
    GUARDWorkspace Cedar

    TENANT_BOUNDARY_VIOLATION

    CHECKED AT GATEWAYEVIDENCE RECORDINGTRC-ORCHID
  • Shortly afterhigh
    GUARDWorkspace Cedar

    SESSION_REVOKED

    CHECKED AT GATEWAYEVIDENCE RECORDINGTRC-ORCHID
  • Thenmedium
    EVIDENCE-STOREWorkspace Cedar

    EVIDENCE_BUNDLE_SEALED

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-ORCHID
  • Thenlow
    D1 INDEXWorkspace Cedar

    EVENT_INDEX_COMMIT

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-ORCHID
  • Thencritical
    SENTINELWorkspace Cedar

    INCIDENT_DECLARED

    CHECKED AT GATEWAYEVIDENCE SEALEDTRC-ORCHID

Simulated scenario on fabricated data. Every identifier, tenant and trace here is invented.

The intelligence theatre

Every system converges. Nothing is drawn that is not there.

The five Sentinel systems report into Command. The eight sectors beyond them are a design direction: this map gives each a place and no data, and says so when you select one.

Illustrative demonstration

Illustrative demonstration

  • Built: reports to Command
  • Design direction: no data connected

Core system · OBSERVE / DETECT

AXIS SENTINEL WATCHTOWER

Built

Visibility per deployment, the transitions and their reasons, and Watchtower health: the last scheduled success, the last status and whether it is stale.

Built: per-deployment heartbeat visibility evaluated every minute by a dedicated scheduled Worker, with its own run history and staleness.

States it reports

  • Full coverage
  • Degraded observation
  • Blind spot
  • Possible suppression
Open Watchtower

Sectors beyond the five core systems (security, infrastructure, financial, operations, vendors, compliance, external and AI systems) are a design direction for Command, shown only as labelled demonstrations.

The authority boundary

The interface shows. The server decides.

The console is static and holds no authority: every privileged decision is made server-side and re-validated there, so the interface can never grant what the API would refuse.

Illustrative demonstration

The operator's role

2 of 6 transitions offered to the analyst role.

  • open to acknowledgedneeds analystOffered
  • open to dismissedneeds commanderNot offered
  • acknowledged to containedneeds analystOffered
  • acknowledged to resolvedneeds commanderNot offered
  • acknowledged to dismissedneeds commanderNot offered
  • contained to resolvedneeds commanderNot offered
  • resolved or dismissed, then any changeno roleNever offered

  • Command decides nothing on its own authority.
  • Every privileged decision is made server-side and re-validated there.

Signal path

What enters it, and what leaves.

Signals in

  • Each system's state through the authenticated API
  • Events, incidents and their timelines
  • Watchtower health, audit completeness and notification delivery
  • The operator's role and tenant

Command

SUPERVISES THE ENTIRE LOOP

Outputs

  • Triage transitions the server accepts
  • Incident declarations and playbook progress
  • Safe Mode engaged and lifted at a scope
  • Authorised responses, recorded with their authority

Ten questions

Command, answered.

The questions every Sentinel system must answer, in the same order on every system page.

Sentinel Command is the operating view: one place where a person sees every system's state, understands it, authorizes a response, acts and verifies the result.

Relations

Where it connects.

  • Guard Receives fromDecisions and containment state
  • Watchtower Receives fromVisibility and Watchtower's own health
  • Range Receives fromNamed results and the release gate
  • Evidence Receives fromPulse, Trace and the integrity of the record
  • Continuity Receives fromPreservation jobs and recovery verification
  • Safe Mode Sends toEngage and lift, by operator authority
  • The operator Exchanges with, outside SentinelState shown; decisions taken within the operator's role
  • Sends to
  • Receives from
  • Exchanges with
  • Outside Sentinel

Failure and health

When it fails, it says so.

In operation

Current

  • Reads are the server's answers
  • Never cached

When it fails or loses visibility

Stale source

  • Watchtower staleness shown beside the estate
  • Pending audit writes surfaced
  • Undelivered notifications surfaced

Command states

  • NominalFull observation. Nothing open.
  • ObservingOpen findings under routine work.
  • DegradedTelemetry incomplete. Visibility is not assured.
  • InvestigatingA declared incident is being worked.
  • ContainedSpread halted. Not yet resolved.
  • Safe ModeDegraded deliberately. High-risk operations held.
  • CriticalActive critical condition requiring response.
  • Current (lit: in operation)
  • Stale source (lit: on failure)

How its own health is verified

  1. Each health fact shown separately
  2. Authority re-validated server-side
  3. Triage transitions enforced by the server

The Sentinel system family

Ten systems, one institution.