CoverProof
Start analysis

Resources / Sample evidence pack

Sample board evidence pack

The PDF below is the exact format CoverProof generates for production board evidence packs. It uses the same renderer, the same PDF/A-3B post-processing, and the same XMP methodology fingerprint embedding. The contents are entirely synthetic — “Acme Capital Partners Ltd” is not a real firm and the named individuals are fictional.

CoverProof-Sample-Evidence-Pack.pdf

PDF/A-3B · ~53 KB · synthetic firm data · no PII

Download PDF

What’s in the pack

  • Cover & firm details. Firm name, FRN, generation timestamp, methodology version slug.
  • Section 250 gap summary. Total individuals, SM&CR-covered, exposed, confirmed gap.
  • Gap individuals. Three named individuals with effective classification, s.250 status, governance coverage, confidence + tier, auditor-grade summary, reasoning steps, reviewer attribution, model id, methodology version, and span-level citations linking the rationale to verbatim s.250 statute text.
  • Declaration audit extract. Lifecycle events (email sent, link accessed, submitted) per individual with UTC timestamps.
  • Counterparty confirmations. Recipient name, company, status, responded-at timestamp.
  • Compliance activity log. Programme milestones (SM&CR import, gap analysis run, declaration cycle).
  • Scope affirmation. The compliance officer’s recorded scope-affirmation entry showing which categories were confirmed in scope at upload time.
  • Methodology appendix. Per-version methodology version, model id, prompt fingerprint (SHA-256), classification counts, Chain-of-Verification outcomes, citations coverage, consensus-tier disclosure.
  • XMP metadata packet embedded in the PDF/A-3B structure — methodology version slugs, prompt fingerprints, and model ids in machine-readable form for a long-term auditor.
  • sRGB OutputIntent embedded per PDF/A-3b clause 6.2.4.3.

What you can verify on the file

  • PDF/A-3B compliance. The file passes structural pre-flight (XMP metadata + OutputIntent present). Independent verification by veraPDF is the authoritative test — our CI runs it on every renderer change.
  • Embedded methodology fingerprints. Open the file in Adobe Acrobat (File → Properties → Description → Additional Metadata) or any XMP-aware tool to inspect the methodology version slugs and prompt SHA-256 fingerprints.
  • Tamper-evidence (in production). Production packs additionally embed an RFC 3161 trusted timestamp from an RFC 3161-compliant TSP. The sample pack does not include this token (TSP issuance is per-customer, per-pack), but the slot is structurally identical.

What this sample does NOT show

  • The exact prompt or statute extract used at classification time. Those are versioned and pinned but not published; see Methodology.
  • An RFC 3161 trusted timestamp (issued per-pack against a real TSP — not present on the synthetic sample).
  • Real-firm noise. Real registers contain abbreviations, legacy role labels, and edge cases the synthetic fixture does not exercise.

Related