A report written to be examined.
Every session ends in a report — on screen, or as a PDF built to last — that explains the preserved record to whoever has to judge it: the summary for the reader in a hurry, the full technical trail for the reviewer who trusts nothing. The report exposes the record; the evidence package remains the record itself.
Everything the session preserved, on one surface.
Identity, summary, evidence, snapshots, custody, logs, package, external proofs, methodology, legal support, and audit — organized for reading, online or as a PDF in an archival format, made to open exactly the same way decades from now.
- An overview cover comes first: session identity, subject, responsible party, inventory, package, custody, external proofs, duration, and timezone — orientation before detail.
- The executive summary is written by rule, from the session's recorded facts — operator, dates, inventory, custody, package, external proofs. The same record always produces the same summary — never an opinion about what the remote content means.
- Grouped navigation with counts keeps long records readable — and section links survive reading-mode changes, so a citation to a report section keeps working.
- Language and time stay anchored to the session: the report renders in the language captured with the session — not the viewer's preference — and timestamps present according to reading mode.
The depth changes. The record doesn't.
One session, three audiences. Reading modes show or hide report sections for each reader — the underlying record is identical in all three.
Essential
The narrative and the evidence, minus the machinery. What happened, what was preserved, and where to find it — for the reader who needs the story, not the internals.
Times in the session's local timeLegal
Adds scope, methodology, custody context, and the legal-support material — the sections counsel reaches for when the report accompanies a filing.
Local time, with the UTC offset spelled outTechnical
Everything — logs, raw references, audit scripts, threat model, and direct entry points into custody verification. For the reviewer who re-runs the math.
UTC first, for precise comparisonSwitching modes never creates a different evidence record — it changes what is displayed, not what was preserved.
The custody chain, from every angle.
From the report's Custody section, a full-screen analyzer opens the same chain — 135 events in the demo session — through complementary views. Click through them below.
- Six views, one chain: table, timeline, sequence, flow, mindmap, and verifier — read events by structure, chronology, actor, or lifecycle stage.
- The verifier re-runs the math in your browser: it redoes the calculation for every event and confirms each link to the one before still holds — automatically, or step by step with pause and speed controls.
- The custody data itself can be downloaded and checked outside the browser — the visual table is never the thing you have to trust.
- Two ways in: a focused verification that starts checking automatically, or the full workspace for deeper analysis — both from the report's Custody section.
A tamper simulation demonstrates detection on a copy of the chain — preserved data is never altered.
Tools for looking closer.
Review happens in the report, on the preserved material — the tools help you examine it, and the originals stay exactly as captured.
- Screenshot comparison — put two captures side by side, slide one over the other, or highlight exactly which pixels changed. The tools help review change; the original screenshots remain the evidence.
- A package viewer in the browser — open the evidence package (a plain ZIP file), browse its contents, and preview files without installing anything. The public viewer checks the package's hash before showing a single file.
- Logs and snapshots, exposed for review — the session log, the network log, a separate log for every site the session touched, and one snapshot per unique page visited.
Analysis reads the record. Nothing here writes to it.
Watch the session back.
The recording plays inside the report — with navigation aids generated from the session itself, so a reviewer finds the moment that matters without watching end to end.
- Chapters mark the session's stops — jump straight to the page where something happened. A short recording with little interaction may simply have none; the report never invents structure.
- Hover the timeline to preview — thumbnail strips let a reviewer scan the whole recording in seconds before committing to a passage.
- The MP4 is the evidence — resolution, frame rate, duration, and codecs recorded as technical metadata, and the file hashed and inventoried in the package like everything else. The player and its aids only help you read it.
The sections that keep the report honest.
A report meant to survive scrutiny states its own method and its own limits. These sections ship in every report — they are part of the product, not fine print.
How the record was produced — controlled environment, hashes, package, custody, external proofs — and the paths to review it.
What the report supports and what it does not attest — legal, factual, and source-truth limits, stated in the report itself.
Covered attacks, verification steps, residual risks, and product limits — written down rather than implied.
Hash, custody, external proof, authenticity, integrity, provenance — defined so non-technical readers follow the same report.
Suggested support text, usage guidance, an attachment checklist, and Word export — drafting aids for counsel to review and adapt, not legal advice.
Commands and sample scripts for package-hash, custody-chain, and external-proof checks — so technical review never depends on trusting the UI.
The report explains. Verification checks.
Everything shown here points at the same record — one that's fully auditable, with or without a Provena account.