Skip to content

Proof

A Proof is the sealed result of one Control test: the Events it read, the root it checked them against, and every exception.

Properties

PropertyTypeRequiredDescription
controlControlrequiredThe Control whose test ran.
namespacestringrequiredThe Startup, Studio, or platform namespace the test read.
fromdatetimerequiredThe start of the range tested.
todatetimerequiredThe end of the range tested.
rootstringrequiredThe published log root the selected Events roll up to.
countintegerrequiredHow many Events the test read.
exceptionsintegerrequiredHow many failed the assertion; each opens an Issue.

Object

JSON
{
  "$id": "https://api.sb/kilnbakery.com/proofs/proof_1",
  "$type": "Proof",
  "control": "control_1",
  "namespace": "Example namespace",
  "from": "2026-10-22T12:00:00Z",
  "to": "2026-10-22T12:00:00Z",
  "root": "Example root",
  "count": 1,
  "exceptions": 1
}

Relationships

  • A Proof proves one Control: the Control whose test the Proof records running over a range of Events. proves, inverse provenBy.
  • A Proof is relied on by many Audits: the Proofs the auditing firm samples across the report period. reliedOnBy, inverse reliesOn.

Verbs

  1. getReturns one Proof by id.
    GET /{namespace}/proofs/{id}readNo Event
  2. listReturns Proofs, newest first, one page at a time.
    GET /{namespace}/proofsreadNo Event

A Proof is kept forever and never edited: it has no update or delete.

Permissions

Which Access level may call each Verb. One-way Verbs wait their delay window.

Operationowneradminmemberviewer
Proof.getYesYesYesYes
Proof.listYesYesYesYes

Call it

Text
Show me the latest proof.

Example

Each night, the Permission decay test for a recipe planner reads 4,812 Events. It finds 0 exceptions and seals a Proof citing the published root.