- Scoped to a project and a
periodStart/periodEndwindow (400 days maximum) - Hash-addressed — content-addressed by its own SHA-256, computed over the exact bytes stored, not over a re-serialized copy
- Immutable once generated — nothing about a completed pack is edited in place; generate a new one for a new period
- Never a compliance certification — see the honesty constraint below
The honesty constraint
Every generated document — Compliance Card or control evidence, in every format — carries this exact disclaimer, printed at both the top and the bottom of the document:“This document reports controls and evidence observed by Zespan for the stated scope and period. It is not a certification of compliance and does not constitute legal advice.”This isn’t boilerplate — it’s the feature’s design premise. A section with no matching records for a period renders the literal text “No evidence available for this period.” — never a suppressed section, never a silently-passing control. See Frameworks and controls for how an uncovered control is surfaced before you even generate a document.
The two document kinds
Compliance Card
Everything Zespan recorded about one agent (or all agents, if you leave the agent unset) for the period: profile, models used, guardrails in force, guardrail change history and outcomes, evaluation results with sample sizes, human approvals, known limitations, and change history.
Control evidence (by framework)
The same underlying facts, reorganized under a framework’s controls — SOC 2, the EU AI Act, or ISO/IEC 42001. Controls Zespan can’t observe are marked Manual evidence required. See Frameworks and controls for what each control draws on.
Generating a pack
1
Open Compliance
From the project sidebar, open Compliance in the Govern group. (In the classic sidebar the page is under Monitor.) Requires the Pro plan. In the shared demo the page is read only: you can read it, but Generate evidence pack is replaced by a sign-up link or a “Read-only demo” note.
2
Choose a document type
Compliance Card for one agent (or all agents), or Control evidence (by framework) for a framework mapping. Control evidence requires picking a framework: SOC 2, EU AI Act, or ISO/IEC 42001 — see Frameworks and controls.
3
Set the period
Pick
periodStart and periodEnd. The form defaults to the last full calendar month. Maximum period length is 400 days.4
Pick a format
HTML (default) or JSON — see Formats below.
5
Generate
Click Generate evidence pack. This returns immediately with the pack in
pending status — generation runs in the background, and the row updates to processing then completed (or failed) as it runs. The Compliance page polls automatically while any pack is in flight.6
View, download or verify
Once
completed, use View to read the document in the app, Download to get the file, or Verify to re-check it — see Viewing a pack in the app and Verification.Organizations with the agent-first interface switched on also see a Not covered line under the Compliance page header. It comes from the same coverage check as the Generate tab, for the framework and period in the form: it names the framework and period it was checked for, how many controls need evidence you supply yourself, and the sections that have no evidence yet. If the coverage check can’t be read, the line is left out rather than guessed. The evidence pack page opens with a plain line that Zespan reports what it observed and does not certify compliance.
AI governance evidence sections
Two evidence sections support the EU AI Act and ISO/IEC 42001 mappings:- AI data governance settings — the project’s server-side PII redaction setting and preset, the prompt storage preference, log retention for your plan, and the organization’s AI processing setting, with every change to it during the period.
- Record-keeping and event logs — how many model-call events Zespan recorded in the period, the first and last event time, and your plan’s retention. If retention is shorter than six months, the document states it as a fact; EU AI Act Articles 19 and 26(6) expect logs of high-risk systems to be kept for at least six months.
Formats
Viewing a pack in the app
View is the main action on every completed row of the Compliance page’s register. It opens the pack at/compliance/packs/{packId} so you can read it without downloading it first. The page has:
- A header with the document (framework and type), the period (UTC), when it was generated and who generated it. In the shared demo the generator is always a fictional name.
- A Contents list on the left, one entry per control and evidence section. Click an entry to scroll the document to that section.
- An Integrity card with the full SHA-256 hash, Copy hash, and a Verify button. Verify runs the same check as Verification and shows the result right there: whether the hash matches, whether the cited records still exist, and any divergences.
- Download to save the file and, for an HTML pack, Print, which opens your browser’s print dialog for the document alone, without the app around it.
compliance:read and the Pro plan), changes nothing, and is recorded in the audit log as compliance.pack_viewed. The dashboard reads the document with GET /v1/projects/:id/evidence-packs/:packId?view=true, which returns the document content in the response on every storage backend (up to 10 MB; above that content is null and tooLarge is true).
Who generated a pack
Each pack in the list shows who generated it. The API returnsgeneratedBy (the user ID) plus generatedByName and generatedByEmail. Both are null if that user has since been removed. generatedByName falls back to the email when the user has no display name.
Failed and stuck packs
A pack that stays inpending or processing for more than 30 minutes is marked failed with a “Timed out” error, so a lost background job can’t leave it spinning forever. The check runs when packs are listed, fetched, verified, deleted, or retried. Self-hosted deployments can change the 30 minutes with the EVIDENCE_PACK_STALE_MINUTES setting.
For a failed pack you can:
- Retry —
POST /v1/projects/:id/evidence-packs/:packId/retryre-runs the same pack with the same parameters. It returns202with{ packId, status: "pending" }, and the timeout counts from the retry. - Delete —
DELETE /v1/projects/:id/evidence-packs/:packIdremoves it and returns204.
409 for a pack that isn’t failed. Completed packs are write-once and can’t be deleted. Retry and delete are recorded in the audit log as compliance.pack_retried and compliance.pack_deleted.
Downloading
GET /v1/projects/:id/evidence-packs/:packId?download=true returns a presigned download URL when packs are stored in object storage (Cloudflare R2), or the raw document content directly when running on local-disk storage (typically self-hosted or local dev). The dashboard’s Download button handles either case for you.
Permissions
A role without
compliance:generate can still list, view, download, and verify existing packs — it just can’t start a new generation, or retry or delete a failed one.
Next steps
- Frameworks and controls — the SOC 2, EU AI Act and ISO/IEC 42001 mappings and what evidence each control draws on
- Verification — what
/verifyre-checks, and what it can’t - Audit log — the record source behind access-control and change-history evidence

