Illustrated demo

See what remains recorded with EVIDE

Two illustrated paths: decisions made by people, and declarations from AI systems.

Invented examples. This page illustrates how the service works: it makes no deposits and generates no documents.

How to read the diagrams

Declared

Entered by the depositor. EVIDE records it as declared; it does not verify it.

Recorded by EVIDE

Assigned or calculated by the platform when the deposit is received.

Referenced only

Stays outside EVIDE. Only a reference, and its fingerprint if declared, is recorded.

Not established

What the record does not prove.

Why it matters

The limit was โ‚ฌ500. Then it became โ‚ฌ200. The AI agent approved โ‚ฌ350. What can you reconstruct?

Which instruction was declared, what changed, which instruction the reported decision referred to, and what supporting material exists: for an integrator or AI lead, these are practical questions. For auditors, experts, authorities and judges, keeping these elements distinct provides concrete material for examining the sequence.

In this example you will see how to:

  1. Record instructions and changes - the initial instruction and the later restriction, each with its declared author and references.
  2. Reconstruct the recorded sequence - linked deposits in a chain, with declared times kept distinct from EVIDE receipt times.
  3. Examine the reported decision - see which instruction the record of the โ‚ฌ350 approval cites, and compare it with the recorded restriction.
  4. Locate supporting material - external references are kept apart from what EVIDE actually received, and what each fingerprint covers is explicit.
  5. Prepare for independent review - understand what the records and the EAR make available for examination, and what the optional FEDIS adds.

EVIDE helps turn a later dispute into an examination of records: declarations, changes, references and reported decisions that can be compared. Establishing which instruction the agent actually received or applied, and whether a violation occurred, requires examination of the supporting evidence.

Build today the records that others may need to examine tomorrow.

The refund limit

Gamma Services uses an AI agent, RA-1, to approve refund requests. The scenario imagines an instruction, a change to it and a decision by the agent. No agent executes anything: the illustration shows how three declarations about these events would be submitted through the API, all from the same account.

The company, the people and the agent are invented.

Three deposits in one chain

Chain position 1
Declared instruction
  • Declared: Autonomous refund limit: โ‚ฌ500
  • Declared: Declarant: Head of Customer Operations
  • Declared: Declared at: 1 Oct, 09:00 UTC
  • Referenced only: Internal instruction document, referenced with its fingerprint
  • Declared: Opens a chain and declares a matter reference
  • Recorded by EVIDE: Chain position 1, assigned by EVIDE
For each deposit: identifier, fingerprint, receipt time and EAR
โ—† chain link
โœŽ declared relation
Chain position 2
Declared change
  • Declared: Limit reduced to โ‚ฌ200
  • Declared: Declarant: Head of Compliance
  • Declared: Declared at: 6 Oct, 14:00 UTC
  • Declared: Declared relation: supersedes the earlier declaration
For each deposit: identifier, fingerprint, receipt time and EAR
โ—† chain link
Chain position 3
Reported decision
  • Declared: Refund of โ‚ฌ350 approved
  • Declared: Threshold declared as met, with reference to the original instruction
  • Declared: Declared at: 8 Oct, 10:30 UTC
For each deposit: identifier, fingerprint, receipt time and EAR

Two kinds of link, two different guarantees

Recorded by EVIDE

Chain link - checked by the server

When a deposit arrives, the server checks that the previous deposit exists, belongs to the same domain as the API key, and is in a valid state. Where both deposits declare a matter reference, the values must match; an omitted reference can be inherited from the parent. The chain documents the links and the order of deposits - not, on its own, the order of events outside EVIDE.

Declared

Declared relation - not checked

Points to the fingerprint of the earlier declaration. The server does not check that it matches an existing declaration. A declared change is not a change applied to the agent.

What remains examinable

What remains examinable

  • the sequence of declarations: โ‚ฌ500, then โ‚ฌ200, then a โ‚ฌ350 decision that declares it relied on the original instruction;
  • two times for each deposit: the declared time and the EVIDE receipt time;
  • the chain positions 1, 2 and 3;
  • the fingerprints of referenced documents, to compare with documents produced later;
  • the EAR of each deposit.
The API also returns an evidentiary profile computed from the declared inputs - for example, continuity is unknown when classification stability and visibility are not declared. It is not a check of the agent's behaviour and not a score of evidentiary strength.
Technical details: where these elements live in the payload
  • decision - type, status finalized, declared closure time, summary.
  • authority - declared id and role; dapi_number must match the DAPI identity bound to the API key.
  • declarations[] (EVIDE ANCHOR) - type, declared value, declarant, declared time; the response returns a declaration_digest for each.
  • declarations[].declared_relations[] - target_declaration_digest, relationship (for example supersedes) and reason.
  • evidence_references[] (EVIDE Artifacts) - pointer, declared origin and relationship, optional fingerprint with scope and author.
  • chain - parent_evide_id, chain_type, matter_reference.
  • intervention.classification_context - required, non-empty object; handoff - required, with boundary_readiness.

The fingerprint of an API deposit covers the whole payload in canonical form, except a top-level content_hash.

Optional on the API path: the ESB (Epistemic Stabilization Buffer), for decisions that need an observation period. When the buffer closes, a new EAR version is generated. Not used in this example.

After the deposit: EAR, optional FEDIS, registry

Evidentiary Artifact Record (EAR)

  • Recorded by EVIDE: Generated automatically by the platform when the deposit is finalised - not on request.
  • Recorded by EVIDE: A plain-text summary of the recorded state of the deposit, which the owner can download with its own SHA-256 checksum.
  • Recorded by EVIDE: When the service generates a new EAR, it creates a separate version rather than overwriting the previous one.
  • Not established: It records what was declared and what the platform computed. It is not a verification of the facts.

FEDIS - optional

Forensic Evidence Declaration & Integrity Statement. The owner can request it at deposit or later, from the record page.

  1. RequestStarts an evaluation and a quote. It does not generate the document.
  2. Evaluation and quoteCarried out by the certifier.
  3. GenerationOnly on the certifier's explicit command.
  4. Qualified electronic signatureApplied by the certifier: a distinct, later step.
  5. Qualified electronic time stampA further distinct step.

What a FEDIS identifies, with SHA-256 fingerprints

For an API deposit, a FEDIS identifies the Canonical Intake Record and the frozen EAR.

  • Not established: The time stamp applies to the FEDIS document when it is affixed; it does not retroactively make the intake time qualified. A FEDIS does not prove the event or the truth of the content, and guarantees neither admissibility nor evidentiary value.

Public registry - a separate step

Optional: publication is the owner's choice. It is possible only after a FEDIS has been issued, and the certifier carries it out on the owner's instruction. It is never an automatic result of a deposit or of a FEDIS.

In this illustrated example no FEDIS is requested and nothing is published.

Go further

Try the API with your own payloads: Governance Lab

A free research environment where you can send your own payloads to the API. Access follows the Lab Procedure: a registration request, then approval. Lab records carry no evidentiary value, and FEDIS, the public registry and chains are not available there.

Request access to the Governance Lab โ†’