AXIS SENTINEL EVIDENCECore system

Ledger. Trace. Pulse.

EVERY MATERIAL EVENT LEAVES A RECORD THAT CAN BE RECONSTRUCTED.

Evidence is Sentinel's institutional record. The Ledger holds durable history, Trace reconstructs the causal sequence, and Pulse states current operational state derived from the record. Raw evidence is preserved apart from its searchable index, with its digest and provenance.

Two Sentinels stand in a dark vault aisle before a sealed door. Crimson visors are lit. Black cases with a gold shield fill the foreground.

Illustrative render. Evidence (Ledger, Trace and Pulse) is built. Evidence Vault is a separate store and is not enabled. Evidence storage is not enabled in this deployment, so the vault here is a picture of that idea, not a live store.

Follow an eventWhat the record proves

Place on the operating loopPRESERVE
  1. 01ObserveContinuous telemetry from every service and edge you connect.
  2. 02VerifyTelemetry checked at the gateway before it is trusted.
  3. 03DetectAnomaly, policy violation, and absent signal alike.
  4. 04ProtectPolicy enforced at the identity and tenant boundary.
  5. 05PreserveEvidence written down before it can be lost. (Evidence operates here)
  6. 06RecoverContinuity coordinated, state restored, result verified.

Recover returns to Observe

Evidence writes the record down before it can be lost.

Three records

Three questions, kept apart.

History is not state, and a causal link is not a log line. The Ledger, Trace and Pulse answer different questions and are never merged into one.

  1. The newest plates of a long row in a dark archive hall, seen close and low: each a black-titanium plate with a hairline of champagne light down its edge, small rings on pins standing off the faces of chosen plates, and a fine gold thread passing through the rings, one branch of it dashed

    Ledger

    What happened

    Plates in strict sequence. Each entry commits to the one before it; the next is added at the head.

  2. The gold thread seen from above the row, passing through rings on pins standing off chosen plates as it runs down the hall, with a dashed branch that leaves it and rejoins

    Trace

    How it happened

    A thread through the records that led from one event to the next. The dashed branch was inferred, and says so.

  3. A slender blade of warm light hung in a four-post titanium lantern on a stepped dais at the head of the row, the thread of gold light running into it and the nearest plates at its side

    Pulse

    What is true now

    Derived from the record and held at the head of it. It says what is true at this moment, not how it came about.

Three cameras in one hall. Illustrative renders.

Chain of custody

From signal to record.

Choose an event and follow it down the vault. Everything upstream of the gateway is a claim; everything downstream is a record. An incident is rebuilt from the last three layers read back, Pulse first, then Trace, then the Ledger in order, then the preserved object checked against its digest, as on the Guard page.

Choose an event

Event chosen: Session revoked at the boundary. The demonstration restarts at the first layer.

Illustrative demonstration

One event, becoming a record

EventSession revoked at the boundary

  1. TelemetryA claim, not yet a record (sealed)
  2. Verified ingestionWho spoke, and how it is known (sealed)
  3. Searchable indexWhere the moment is found (sealed)
  4. Preserved raw objectThe original, kept apart (sealed)
  5. Hash and provenanceA digest and a lineage (sealed)
  6. LedgerWhat happened (sealed)
  7. TraceHow it happened (sealed)
  8. PulseWhat is true now

After: Telemetry

A claim
Source
A privileged session
Presented as
An observation
How it is known
Named on the record.

Illustrative values. Digests and positions here are not measurements.

After: Verified ingestion

Admitted
Registration
Identifies, authorizes nothing
Origin
Registered and proven
Already seen
Not a new report
Budget
Within its allowance
Known as
Server observed

Illustrative values. Digests and positions here are not measurements.

After: Searchable index

Indexed
Store
Event index
Holds
Metadata and a pointer
Triage
Open

Illustrative values. Digests and positions here are not measurements.

After: Preserved raw object

Stored
Store
Object storage
Key
tenants/‹tenant›/evidence/‹id›
Type
Guard decision
Row
Pending, then stored
Storage
Verified per deployment

Illustrative values. Digests and positions here are not measurements.

After: Hash and provenance

Unverified
Digest
A SHA-256 digest is recorded
Provenance
Tenant, source, attestation, capture time
Integrity
Not yet re-read

Illustrative values. Digests and positions here are not measurements.

After: Ledger

Appended
Action
Session revoked
Actor
Operator
Previous
••••
Entry
••••

Illustrative values. Digests and positions here are not measurements.

After: Trace

Linked
Observation to event
Observed as · server attested
Event to decision
Decided by · operator entered
Decision to object
Evidenced by · server attested
Object to entry
Recorded in · server attested

Illustrative values. Digests and positions here are not measurements.

After: Pulse

Derived
Session
Revoked
Evidence
An object, unverified
Audit
Complete
Operational state
Observing

Illustrative values. Digests and positions here are not measurements.

Step 8 of 8

Pulse

Pulse derives what is true now from the record: the session is revoked, one object is stored and not yet re-read, and the audit is complete. This is what is true now.

  1. A privileged session acts outside its usual pattern. At this moment it is only an observation: something a source says, not yet a record.

  2. Sentinel decides who is speaking from the estate on file, not from what the report claims about itself, and names how the record is known. This one Sentinel observed itself.

  3. The event is indexed so an investigator can find this moment without replaying an estate's history. The index holds metadata and a pointer. Bulk content never enters it.

  4. The original bytes are written, unmodified, to object storage, apart from the index. The row says pending until the object is confirmed, and only then stored. Where storage is not verified, this step is refused rather than faked.

  5. A SHA-256 digest is taken over the exact bytes and recorded with their provenance. The object starts unverified: stored, but not yet re-read. A later re-read compares the bytes with this digest.

  6. An operator revokes the session. The action is appended to the tenant's hash-chained Ledger, and the entry commits to the one before it. This is what happened.

  7. Trace links the observation to the event, the decision, the evidence object and the Ledger entry. Every link records how it is known, so an inferred link is never read as an observed one. This is how it happened.

  8. Pulse derives what is true now from the record: the session is revoked, one object is stored and not yet re-read, and the audit is complete. This is what is true now.

Simulated states, written to show how the system behaves. Nothing here reads or changes a live system.

A collar of black titanium seated on a plate in the row, a hairline of light closed round it, the gold thread beyond and the lantern of warm light behind
SealedA collar seated on a plate and a hairline of light closed round it. Illustrative render.

Integrity

What the record can prove, and where it stops.

Each Ledger entry commits to the one before it, so a silent edit to a single entry can be found by re-walking the chain. Try three changes and see what the re-walk reports. The last is the limit, and it is stated.

Illustrative demonstration

Simulate a change to the record
  1. Entry 1

    Incident declared

    Intact
    Commits to
    ••••
    Stored hash
    ••••
  2. Entry 2

    Session revoked

    Intact
    Commits to
    ••••
    Stored hash
    ••••
  3. Entry 3

    Decision snapshot preserved

    Intact
    Commits to
    ••••
    Stored hash
    ••••
  4. Entry 4

    Incident marked contained

    Intact
    Commits to
    ••••
    Stored hash
    ••••

Re-walk result: every entry commits to the one before it. The chain is intact.

A matching digest shows

  • The stored bytes are, byte for byte, the bytes whose digest was recorded at capture.
  • The object has not been silently altered or truncated since capture.

It does not show

  • Who created the content.
  • That the observation was truthful, or that the event it describes occurred.
  • That the digest recorded at capture described what the observer meant to capture.
  • That the Ledger chain has not been rewritten by someone who can write to the database.

Sentinel preserves evidence and makes its integrity checkable. It does not assert legal admissibility or certify compliance with any regime: that assessment belongs to counsel and auditors.

The vault with storage not enabled: the row of plates and the lantern present but dim and dark, the collar stopped part-way down, one short amber hairline marking the plate that was refused
The vault, darkThe vault with storage not enabled: present, and dark. Evidence is refused, not faked. Illustrative render.

The vault door

Evidence storage is verified per deployment.

Evidence on this page is the built record: Ledger, Trace and Pulse. Evidence Vault, the gated object store, is a separate capability and is off. A connected store is configuration, not proof. Sentinel proves storage from both sides before it describes it as available, and a service without verified storage refuses evidence rather than record objects it has not stored.

Illustrative demonstration

Choose a state Sentinel can report
  • Not establishedA store is connected for this service
  • Not establishedA check is written, read back, and matches
  • Not establishedThe scheduled check reads the same object from the same store
Not connected

No store is connected for this service.

Refusing evidence: no store is connected. There is no fallback to local storage.

These are the states Sentinel can report for a deployment. This page does not report the state of any deployment.

Signal path

What enters it, and what leaves.

Signals in

  • Records admitted by First Light and server-observed events
  • Guard decisions and operator actions
  • Raw evidence objects and their digests
  • Preservation confirmations and Shield records

Evidence

PRESERVE

Outputs

  • Ledger: what happened
  • Trace: how it happened
  • Pulse: what is true now
  • Integrity state per object: verified, unverified, mismatched or missing

Ten questions

Evidence, answered.

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

Evidence is Sentinel's record: the Ledger holds what happened, Trace reconstructs how it happened, and Pulse states what is true now, derived from the record.

Relations

Where it connects.

  • First Light Receives fromAdmitted records and server-observed events
  • Guard Receives fromEvery decision, written with the change
  • Continuity Receives fromPreservation outcomes, recorded to the Ledger
  • Shield Receives fromShield records preserved as evidence objects
  • Range Receives fromLedger and evidence failure scenarios
  • Command Sends toPulse, Trace, and the integrity of the record
  • Object storage Exchanges with, outside SentinelRaw objects written and re-read; verified per deployment
  • Sends to
  • Receives from
  • Exchanges with
  • Outside Sentinel

Failure and health

When it fails, it says so.

In operation

Verified

  • Objects stored apart from their index
  • Digests re-read and compared

When it fails or loses visibility

Refusing evidence

  • No verified storage: evidence refused, not faked
  • No fallback to local storage
  • A failed audit write shown as failed

Evidence states

  • Verified (lit: in operation)Stored, re-read and matched to its digest.
  • UnverifiedStored, not yet re-read. Not a failure, not a confirmation.
  • Integrity mismatchThe bytes no longer match the recorded digest.
  • MissingRecorded, but the object is not where it should be.
  • Refusing evidence (lit: on failure)No verified storage. Evidence is refused, not faked.

How its own health is verified

  1. Storage proven from both sides with a probe object
  2. Ledger chain re-walked
  3. Mismatches counted, never averaged away

The Sentinel system family

Ten systems, one institution.

Put Sentinel on guard

Choose the protection level built for where your company is today.

View plansStart with Sentinel