Glossary
Seal
The method that turns a proof record into its digest: Seal v6, frozen.
Read the termGlossary · Term 31 of 39
Proof record
A proof record is the 16-field record elan1 writes for every action an AI agent proposes, whether it is allowed or refused. It holds who acted, what was proposed against which record, which declaration and rules version applied, and the digest of the previous record; the outcome and approver are shown beside it. Records are SHA-256 hash-chained, and there is never a seventeenth field.
In one sentence: The 16-field record written for every action, allowed or refused; SHA-256, chained. "No seventeenth field, ever."
01In more detail
What it means in practice
Each record is hashed with SHA-256 over a length-prefixed preimage and chained to the one before it. Change a past record and the chain shows it. That is what tamper-evident means at L1.
Evidence rows cannot be updated or deleted. Wherever another surface shows a Govern decision, it carries one line: "Checked and recorded by elan1 Govern."
02Where this shows up in elan1
Rung 8 PROOF; every specimen on this site; the CA console in elan1 Work.
04Questions
Proof record: common questions
Exactly 16 fields, from F01 tenant_id to F16 recorded_at: who asked, what was proposed, which declaration and version applied, which rules and gates ran, who approved, the autonomy level, the outcome and the previous record's digest. The record is sealed under Seal v6 with SHA-256.
Yes. Every write intent ends in a proof record, whether it is allowed or refused. A refusal is metered at 0.4 of a governed action.
Defined in the elan1 glossary · Last reviewed 10 Oct 2026. Definitions change only with a dated note.
// SEE IT
See the term in a governed action.
The walkthrough follows one write from intent to proof record, using the words in this glossary.