Evidence package · engagement B
The retainer keeps it ready. Activation produces the bundle.
Two things are bought here, and they are not the same thing. The retainer buys a rehearsed, provisioned, restorable position before a contest. Activation buys one evidence bundle to a fixed standard, verifiable without us.
Retainer · standing
What the retainer holds ready
- Tenant provisioned and held for the client.
- Country packs loaded for the contests in scope.
- Capture and chain of custody rehearsed against the client's own field structure.
- Official-source reachability rehearsed against the real endpoint.
- Monitors proven restorable from backup, not merely running.
The retainer publishes no figure. It buys readiness.
Activation · one contest
What activation produces
Activation on a declared contest date produces one evidence bundle to bundle standard erm_evidence/1: eight parts, a manifest, a chain root over the parts, and a delivery hash. It is verifiable offline — checking it requires no Veridian service, no account, and no network call to us.
erm_evidence/1 Verifiable offline 8 parts
One activation, one contest, one bundle. Activation is never retroactive.
Exhibit index
Eight parts, fixed by the standard
The index is fixed: a bundle with a missing part is not an erm_evidence/1 bundle. Where a part cannot be produced, it is present and states why.
Manifest
A SHA-256 for every part in the bundle, plus the chain root computed over those hashes, and the delivery hash the custody record carries.
Capture set
Aggregate unit keys, the capturing role rather than any individual identity, and the image hash taken at capture.
Content-credential chain
C2PA-ready, and stated as C2PA-ready: the chain is structured for C2PA assertions and is not certified by any C2PA authority.
Extraction and verification records
A tamper-evident chain of records. Each record carries its own proving basis, per record and never in aggregate.
Human-confirmed · production-proven Automated · simulation-proven
Official-record snapshot
The source, the exact URL, the fetched-at timestamp with its zone, and the content hash of what was fetched.
Reconciliation report
Line-by-line deltas against the snapshot, with the full N/A log. Every N/A carries a reason; absence is never a zero or a blank.
Audit-log slice
The engagement's log entries for the period, contiguous and numbered, so a gap is visible as a gap.
Custody record
Every custody event for every artifact, with the five-step verification procedure printed alongside it.
What a court receives
One hash, five steps, and three failures we can prove we detect
Delivery hash
issued with the bundle, not on this page
The delivery hash is issued with the bundle and read into the record on delivery. No engagement hash is published on this page.
Verification procedure · 5 steps
- Recompute the delivery hash (SHA-256 over items, chain_root, bundle_id) and compare it with the custody record.
- Recompute the SHA-256 of every part and compare it with the manifest.
- Recompute the chain root from the part hashes.
- Re-fetch the official-record snapshot URL and compare its content hash.
- Replay the reconciliation report against the capture set and the N/A log.
Tamper cases detected in CI · 3 of 3
Altered tally-sheet image
Detected as a part hash mismatch at step 02.
Reordered or removed capture entry
Detected as a chain root mismatch at step 03.
Substituted official-record snapshot
Detected as a content hash mismatch at step 04.
All three cases are exercised on every CI run against a synthetic bundle. Three cases constructed, three detected. Cases beyond these three are not claimed.
Bundle sample · synthetic CI fixture · not an engagement Sample · CI fixture · not live
Shape of the bundle only. The hashes below are synthetic, produced from a CI fixture, and correspond to no contest, no station, and no official record.
erm_evidence/1 ├── 01_manifest.json sha256:9f2c… chain-root sha256:04ae… ├── 02_capture_set.jsonl sha256:7b31… 1,412 entries ├── 03_content_credentials/ sha256:c58d… C2PA-ready ├── 04_verification/ sha256:2d90… 1,412 records ├── 05_official_snapshot/ sha256:e417… fetched 24 Jun 2026 08:12 UTC ├── 06_reconciliation.json sha256:aa06… N/A entries: 14 ├── 07_audit_log.slice sha256:31f8… entries 3,904–4,118 └── 08_custody_record.json sha256:6c2b… events: 268
Pricing
On the published card; combined floor US$75,000.
Published card · floor
Retainer and activation are priced separately and published together, so a buyer can see what readiness costs and what the bundle costs. Neither price moves with the contest or with the principal.
Retainer
US$30,000
on request · published card
Activation
US$75,000–250,000
on request · published card
Sovereign floor
US$150,000
on request · published card
Internal figures. Not published on veridianelectoral.com; the public card carries the combined floor only.
Request an engagement
Tell us the contest, the date, and the artifact you need. We reply with scope, refusal conditions, and a price against the published floor.