A black Sentinel at a standing terminal. The visor and a slot on the rack are lit crimson.

Developers

Integrate a service in four steps.

A service that cannot be observed cannot be defended.

  1. Send reports

    Your service sends a report of what it did. Sentinel accepts the report only when it belongs to your estate, and keeps a note of how the report is known.

  2. Say what you expect

    Tell Sentinel what the service should report, and how often. Watchtower compares what arrived with what you expected, so silence is noticed instead of assumed to be fine.

  3. Name who acted

    Include who acted, and which part of the estate the report belongs to. Guard can then apply your rules, and Trace can show how a decision spread.

  4. Read state, do not poll logs

    Pulse shows what is true now. Ledger and Trace answer what happened. Reading these is clearer than reconstructing the same facts from raw logs.

Sentinel integration stays small: send reports, say what you expect to send, name who acted, and read state back from Pulse rather than reconstructing it.

Event shape

What an event looks like on the wire.

A sample ingestion window. Each line carries its source, action and scope.

Illustrative demonstration
Earlierservice-a · access check · example-app · allowedCHECKED
Earlierexample-app · sign-in challengedCHECKED
A moment agopayments-service · privileged session openedCHECKED
A moment agoservice-b · copy running behindCHECKED
Just nowwatchtower · service-c · gone quietUNCHECKED
Nowevidence · record sealedCHECKED
Illustrative shape onlySample reports only. Credentials are issued per deployment and are never published here.

Validation

Your integration is exercised in Range.

A new source is not considered integrated when it first delivers an event. It is integrated when Range has confirmed that its telemetry survives queue failure, that its silence is detected, and that its tenant scope holds under a forged claim.