SENTINEL FIRST LIGHTOperating layer

The nervous system beneath the platform.

EVERY SIGNAL ENTERS THROUGH ONE TRUST BOUNDARY.

First Light is Sentinel's internal nervous system. Today the gateway admits browser event classes from a registered page, checked at one trust boundary. AXIS services and the Cloudflare edge are a design direction, not a live source.

Dawn on a dark facade. A crimson line crosses the glass and a gold shield lights at the entrance.
Place on the operating loopOBSERVE / VERIFY
  1. 01ObserveContinuous telemetry from every AXIS service and edge. (First Light operates here)
  2. 02VerifyTelemetry checked at the gateway before it is trusted. (First Light operates here)
  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.
  6. 06RecoverContinuity coordinated, state restored, result verified.

Recover returns to Observe

First Light carries what is observed and checks it before it is trusted.

One signal, three records

What is kept is kept in three views.

Evidence keeps each record as a Ledger of what happened, a Trace of how it happened and a Pulse of what is true now. Each still says how it is known.

  1. A stack of thin titanium plates with a gap in the middle that a flat ribbon of fine light fibres slides through, each plate edged with a hairline of champagne, standing on a small plinth.

    LedgerWhat happened. A plate laid on for everything kept.

  2. A fine coil of platinum wire with a thread of champagne light wound round a flat ribbon of light fibres, held between two turned collars.

    TraceHow it happened, laid out along its length.

  3. A turned platinum ring on a slender stand with a ribbon of light fibres passing through it and two thin concentric rings of light round it, in front of the bright aperture.

    PulseWhat is true now, and still true a moment later.

The system map

Everything upstream is a claim. Everything downstream is a record.

One gateway stands between what a page says and what Sentinel records. It resolves who is speaking from the verified origin, never from the request body. What is built is drawn solid. A design direction is drawn dashed and carries no signal.

Illustrative demonstration

One observation, through the trust boundary

  1. Upstream: claims
  2. Registered pagesBuiltA registered deployment's Site Agent reports what its page observed. A claim until the gateway admits it.
  3. AXIS servicesDesign directionA source in the design. The gateway admits browser observation classes only today.
  4. Cloudflare edgeDesign directionA source in the design. Cloudflare is the network provider Guard asks for containment today.
  5. Signed SCEF telemetryDesign directionSigning service telemetry at its source is a design direction. Nothing is signed or checked as signed today.
  6. The trust boundaryEverything upstream of the gateway is a claim. Everything downstream is a record.
  7. Downstream: records
  8. IngestionBuiltThe one entry. It refuses a request without an Origin and a batch that is empty or too large.
  9. VerificationBuiltKey, origin, proven domain, budget, replay, contract and tier. Not a signature.
  10. NormalizationBuiltIdentity from the registry, time stamped by the gateway, and how the record is known.How it is known: site reported
  11. DetectionBuiltWatchtower evaluates the heartbeats on a scheduled pass. Silence becomes a finding.How it is known: server observed
  12. D1 event indexBuiltEvery observation is written to exactly one table: telemetry or events.
  13. Raw evidenceBuilt, gatedRaw objects, kept apart from the index with a digest. A deployment without verified storage refuses evidence.
  14. Ledger, Trace, PulseBuiltWhat happened, how it happened, and what is true now, each still saying how it is known.
  15. CommandBuiltEach record shown with how it is known, and Watchtower's own health beside it.

Step 9 of 9

Command

Command shows each record with how it is known, and Watchtower's own health beside it. A source that has gone silent is shown as silent, never as healthy.

  1. A registered page reports an observation with its public deployment key, from its own origin. Until the gateway admits it, it is only a claim. The dashed sources, and signing at the source, are a design direction.

  2. The Edge Gateway is the one entry. It refuses a request with no Origin, and a batch that is empty or too large. This is the trust boundary: nothing crosses it without being checked.

  3. The key must name an active deployment and the Origin must match the registry. Then budget, replay, contract and tier are checked. No signature is verified: nothing is signed today.

  4. The gateway seals each accepted observation into an envelope: identity from the registry, never the request; time stamped by the gateway; and how the record is known, site reported at most.

  5. Watchtower evaluates the heartbeats on a scheduled pass every minute. A deployment that goes quiet becomes a finding, raised as a server-observed event. The cause is not guessed.

  6. The published contract names exactly one destination for every observation: telemetry for measurement, events for anything a person would triage. It is written to that one table, never to both.

  7. Where a record is kept as an evidence object, the raw bytes are stored apart from the index, with a digest. This needs verified storage: a deployment without it refuses evidence rather than faking it.

  8. Evidence keeps the record in three views: the Ledger holds what happened, Trace how it happened and Pulse what is true now. Each record still says how it is known.

  9. Command shows each record with how it is known, and Watchtower's own health beside it. A source that has gone silent is shown as silent, never as healthy.

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

The stream

Every observation says where it stopped, or where it went.

Each row is a class from the published contract, with how it is known, the gateway's own nine checks in order, the verdict, and the one place an accepted observation is written.

Illustrative demonstration
  1. AGENT_HEARTBEATSealed into an envelope, identity from the registry.site reportedAcceptedtelemetry
  2. PAGE_VIEWEDMeasurement, never triaged.site reportedAcceptedtelemetry
  3. CONTENT_COPY_INITIATEDA person may want to see this one.site reportedAcceptedevents
  4. AGENT_HEARTBEATDuplicate observation.site reportedRejectednothing
  5. DISPLAY_CAPTURE_STARTEDNot permitted at this deployment's protection tier.site reportedRejectednothing
  6. VISIBILITY_DEGRADEDWatchtower's pass found a deployment gone quiet. The cause is not guessed.server observedRaisedevents

Nine checks, in the gateway's order: an origin is present, the key names an active deployment, the domain is proven and the origin matches the registry, the batch is bounded, the deployment's budget allows it, each observation fits the published contract, the protection tier permits that class, it is not a replay, it is sealed with how it is known. A rejected observation is written nowhere. None of these is a signature: nothing is signed today.

First Light streamWritten to show the shapes a stream has. Nothing here is a live record, and no count, time or rate is claimed.

Verification, as built

It checks who is speaking, not a signature.

First Light checks a deployment, an origin, a budget, a replay, a contract and a tier, in a fixed order. Signed telemetry is a design direction: nothing is signed today, and no record says it was. Choose a batch to see where the gateway stops it.

Illustrative demonstration

A batch arrives

The gateway's checks, in order

  1. An Origin is presentPassed
  2. The key names an active deploymentPassed
  3. The domain is proven and the Origin matches the registryStopped here
  4. The batch is boundedNot reached
  5. The deployment's budget allows itNot reached
  6. Each observation fits the published contractNot reached
  7. The protection tier permits that classNot reached
  8. It is not a replayNot reached
  9. It is sealed with how it is knownNot reached

Refused403, deployment rejected

“That deployment cannot report here.”

A key identifies a deployment and authorises nothing. Authority is the pair of the key and the origin the registry holds, and ownership of the domain must have been proven. Script on another site sends that site's origin.

Not among the checksVerifying a signature. Nothing is signed today, and signing service telemetry at its source is a design direction.

Provenance

Every record says how it is known.

A flag that says verified has no room to say how. First Light replaced it with a ladder that names the strongest thing that actually happened to a record, and the label names the route, never a verdict.

  1. inferredBuiltSentinel inferred this from indirect signals. It may be wrong.Where Sentinel infers an activity from indirect signals, such as a suspected developer-tools session. A guess, with a reason.
  2. site reportedBuiltA registered deployment reported this. Sentinel verified which deployment was speaking, not that the activity occurred.Everything a registered page's Site Agent reports. The highest a browser's report can ever reach.
  3. server observedBuiltSentinel's own server observed this directly.What Sentinel's own server observes: a heartbeat that stopped arriving, a decision it made.
  4. edge observedNot reachableSentinel observed this at the edge, before any other system could alter it.No mechanism attests at the edge, so no record may claim it. An attempt to over-attest is refused, not clamped.

Signal path

What enters it, and what leaves.

Signals in

  • Observations from registered deployments (browser event classes; other sources are a design direction)
  • A public deployment key and the registered origin
  • Proven domain ownership
  • The published event contract

First Light

OBSERVE / VERIFY

Outputs

  • Admitted records with authoritative time and attestation
  • Heartbeats for Watchtower
  • Events and telemetry, each in exactly one store
  • Refusals: unknown key, foreign origin, replay, exhausted budget

Ten questions

First Light, answered.

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

First Light is Sentinel's internal nervous system. Today the gateway admits browser event classes from a registered page, checked at one trust boundary. AXIS services and the Cloudflare edge are a design direction, not a live source.

Relations

Where it connects.

  • Watchtower Sends toHeartbeats and telemetry arrival
  • Evidence Sends toAdmitted records, indexed and preserved
  • Guard Sends toAttested observations to act on
  • Shield Exchanges withShield signals admitted within the tier
  • Presence Sends toWhether a page's batches were accepted
  • Command Sends toRecords an operator can rely on
  • AXIS services and Cloudflare Receives from, outside SentinelA design direction: the gateway admits browser event classes only today
  • Sends to
  • Receives from
  • Exchanges with
  • Outside Sentinel

Failure and health

When it fails, it says so.

In operation

Admitted

  • Key, origin, replay and budget checked
  • Attestation assigned at the gateway

When it fails or loses visibility

Refused

  • Unknown key, foreign origin, replay or budget refused
  • Heartbeats keep a reserved budget
  • Over-attestation refused, not clamped

First Light states

  • Admitted (lit: in operation)Key, origin, replay and budget checks passed.
  • ThrottledDeclined under the ingestion budget. Liveness keeps its reserve.
  • Replay refusedSeen before inside the replay window.
  • Refused (lit: on failure)Unknown key, foreign origin or unproven domain.

How its own health is verified

  1. No record may claim edge attestation
  2. The reserved budget is proven bounded
  3. Every event class has one destination

The Sentinel system family

Ten systems, one institution.