Skip to main content
Early pricing is live. Start free for up to 3 AI systems — no card, no time limit.Early pricing is live. Free for up to 3 AI systems.
All docs
How-to guide

Generate an audit pack

Produce the integrity-hashed package an auditor can verify, and know who may do it.

5 minFor: Finance reviewer, Workspace owner

An audit pack is an integrity-hashed package you hand to your auditor: one immutable reporting snapshot, the Board PDF built from it, and an audit ZIP with the evidence behind it. The page is Audit pack at /audit-pack.

Who can generate one

ActionRoles
Generate a Board and audit reportAdministrator, Governance lead, Attestor
Download the audit archiveAdministrator, Governance lead, Attestor, Auditor
Download raw financial evidenceAdministrator, Governance lead, Auditor
Read the audit logAdministrator, Governance lead, Auditor

Everyone else sees the list of packs and the explanation, without the generate control. See Roles and permissions.

Generate

  1. Open Audit pack. Existing packs are listed with their snapshot hash.
  2. Click Generate Board and audit reports (shown as Generate audit pack when the list is empty). One action creates or reuses one server snapshot, the Board PDF and the audit ZIP together.
  3. Open Board (/board) to read the snapshot. Board values never come from a live recompute; the page refetches the stored snapshot and checks its identity before it shows a number.

Expected result

A new pack in the list with Snapshot SHA-256 and a download for the ZIP. The generation is one entry in the audit chain.

Caution

A snapshot is immutable. Generate one at period close, after the evidence it should hold is final-attested; a later change to the record makes a new snapshot, not a changed one.

Verify

The pack's integrity hash is SHA-256 computed over the pack's contents. A reviewer recomputes it on the file they received and compares it with the Snapshot SHA-256 on the page. Each source file inside the pack carries its own SHA-256, so a single changed file is found.

Downloads are authenticated: the page fetches the file with your session and hands it to the browser, because the endpoint is scoped to your organization and would refuse a bare link.

Hand it over

  • Give the auditor the ZIP, the Board PDF and the hash on the page, each from the same pack.
  • Give them the Auditor role if they need to read the Audit log (/audit-log) and use Verify chain themselves. The role reads everything and writes nothing.
  • Point them at what Verify chain does not prove, so the pack is read for what it is.

Previous

Add costs and use cases

Last documented 2026-11-18 against master fb17e1c5. Live release 0.3.1.