SaibleDocs
Evidence

Chains, checks and the evidence pack

Each record is chained to the one before. Change one and the chain names it.

record 1prev = hash 0hash 1 = sha256(prev + record)record 2prev = hash 1hash 2 = sha256(prev + record)record 3prev = hash 2hash 3 = sha256(prev + record)record 4prev = hash 3hash 4 = sha256(prev + record)Edit record 3: the verifier names it
Tamper-evident: every record holds the hash of the one before
saible-evidence-<run>.zipREADME.mdhow to check each hashmanifest.jsonevery hash, in one placepolicy-v<n>.md · .jsonthe policy that decidedendpoint-catalogue-v<n>.csvassessment-records.csvregisters/DORA, GDPR Art. 30, AI Actledger/request records · optionaldecision-records.jsonlsegment-manifest.jsoninstance-keys.jsongateway public keysreadiness/optionalapprovals/who approved what · optionalexposure/the exposure report, as it stoodMANIFEST.JSON HOLDSchainHeadHasheach record's hashpolicyContentHasheach register's hashsegmentSha256Before the zip is written, your browserhashes the records it received and checksthem against the server's segmentSha256.Signed: each record a gateway wrote,by the instance that wrote it.The pack as a whole is not signed.
The evidence pack · what is in the zip
Evidence held
the records evidence this article
Partly held
some of it; the rest is named
Not yet
nothing held yet; your step or Saible's
Readiness: a map of evidence held per article, never a score
Do it
  1. 1On Ledger, press Verify the chain.
  2. 2Open Readiness: per article, evidence held, partly held, or not yet.
  3. 3Open Evidence pack, choose what to leave out, and download the zip.
  4. 4Hand it over with its README.md: it says how to recompute each hash.
For your agents

This topic is also written as Agent Skills your agents can load: ledger, evidence-pack, readiness, registers, evidence-ledger, incidents, ai-literacy. Ask us for them.

Next · Control Plane · ContextWhat each tool is wired to →