Skip to main content
An auditor in round glasses checks a printed record with a magnifier, a crimson seal on the page and a laptop beside it

Verify a record

Check the record without asking us.

Your auditor can verify an elan1 Govern record offline, with one command, without trusting elan1.

Try it on a specimen

How do you verify an AI agent audit record?

Export the record from the elan1 console as one file, then run the open-source govern command-line tool on your own machine. As designed, govern verify checks every signature, the hash chain, the sequence and the fields, and prints one answer. It needs no account and makes no network call, so your auditor need not trust elan1.

How it works

Three steps, no account needed.

  1. Export the record

    Download the record for any period from the console, as one file. It is yours to keep, and stays yours if you leave.

  2. Get the verifier

    The open-source govern command-line tool runs on your own machine. It needs no account and makes no network call.

  3. Run one command

    govern verify reads every record, checks every signature and link, and prints one answer.

Terminal

# Offline. No account, no network call.govern verify kolam-2026-11.recordRecords        412 (#000001 to #000412)Fields         16 per record, all presentSignatures     412 of 412 validSequence       no gapsChain intact
Illustrative output. Kolam Components is a fictional company.

What is checked

Four checks on every record.

01

Signatures

Each record is signed when it is written. The verifier checks every signature against your organisation’s key.
Designed

02

The hash chain

Each record carries the hash of the one before it. An edit, deletion or insertion anywhere breaks every link after it.
Designed

03

Sequence

Records are numbered in order. A missing number is reported, so a record cannot quietly disappear.
Designed

04

Fields

All 16 fields are present in every record: who proposed, what, under which rule, the outcome and who decided.
Designed

Results

What each answer means.

Verifier outputs and what they mean
OutputMeaning
Chain intactEvery record is present, signed and linked to the one before it. Nothing has changed since it was written.
Chain broken at #nRecord n, or the one before it, was edited, removed or inserted after it was written. The verifier names the first break.
Signature invalid on #nRecord n was not signed by the key on file for your organisation.
Sequence gap after #nOne or more records are missing after record n.

Limits

What a clean chain does not prove.

Verification proves the record has not changed. It does not prove the decisions in it were right.

  • It does not say your rules were well written. That is a question for your risk owner and auditor.
  • It does not say an approver read carefully. It says who approved, and when.
  • It does not cover actions taken outside elan1 Govern, in systems agents can reach some other way.
  • It relies on your organisation's signing key being kept safe, as any signature does.
A man in a navy shirt signs off a paper document at a dark desk, seen from above

Specimens

Read a record before you trust one.

Four specimen records show the 16 fields for each outcome: allowed, approved, refused and expired. Every value is illustrative.

See the specimensWhat is a hash chain?

Intelligence you can answer for.

Start with one process. Add the next when it holds.

Contact usSee a governed action