SaibleDocs
Ledger

Contents of a decision record

Where personal data was found and what was decided, never the text itself.

THE REQUESTCustomer ••••••-•••• asks …920Forwarded to the provider. Never stored in the record.{ type: "CPR", start: 9, end: 20 }The record keeps the position and the type.ONE DECISION RECORDORIGINappthe applicationteamits teamcaller_refpseudonymised user, not a nameDETECTIONSdata_classfor example pii_cprdetectionstype, start, endredactionstype, position, tokenPOLICY IN FORCEpolicy_id · policy_versionpolicy_content_hashbundle_revisionthe policy revisionDECISION OUTCOMEactionallow to denychosen_endpoint_idexcluding_rulethe rule that actedaction_would_have_beenrecord-only, advisoryUSAGE AND LATENCYtokens_in · tokens_outcost · latency_msPOSITION IN THE EVIDENCE LEDGERinstance_id · instance_seqrecord hashlinked to the one beforeinstance signaturethe gateway's own keyNo prompt and no answer. Positions and types only.
One request and its decision record. The example detection is taken from the conformance test set.
Steps
  1. 1Open Ledger and choose an Application.
  2. 2Open one decision record. Read its decision outcome, the model endpoint and the rule that acted.
  3. 3Under record-only mode or an advisory rule, read what enforcement would have done.
  4. 4Press Verify chain on the decision record, or Verify the chain on the Ledger.
For your agents

This topic is also documented as Agent Skills that your agents can load: ledger. Request them from Saible.

Next · Gateway · ControlEmergency stops →