Skip to main content
Customer guide

Evidence export and verification

Check a scoped decision record or examination package and state what it cannot prove.

For: Evidence custodian, Auditor, Examiner

Before you begin

Choose an authorized reporting period, governed source and recipient. Arrange permission to export decision metadata; avoid raw customer content and keep an independent copy of the package for verification.

  1. Write down the UTC reporting window and population.
  2. Confirm the recipient may receive the selected material.

Supported scope and current status

The public verifier checks entries present, linked sequence and signed-checkpoint coverage. A signed examination package names its period and verifies its packaged entries; neither check proves every event was recorded.

  1. Read /verify for the four chain verdicts.
  2. Use /examination-package for package contents and stated limits.

Compare this path with the published coverage table and the coverage guide.

Set up the path

Use the release-specific authorized export procedure for a period-scoped, content-free package. Keep original vendor-only test media and private runbooks out of the customer export.

  1. Confirm the package period and expected sources before download.
  2. Use the standalone verifier on a separate trusted system.

Use the workflow

Export the selected period once under the authorized role, transfer it to the reviewer, then run the supplied verification command on that exact file.

  1. Preserve the downloaded bytes and manifest together.
  2. Record the verifier verdict and any uncovered tail.

Verify the result

Check signatures, digests, declared population and period. A changed entry, missing key, broken sequence or uncovered tail needs its own verdict; “verified” applies only to what was actually checked.

  1. Compare the manifest window with the requested window.
  2. Run a deliberate tamper check on a copy if your procedure permits it.

Coverage references: 21 requirements, 0 currently passed

This guide is bound to 21 requirements in RedactWall's acceptance crosswalk, which is maintained internally and not published. A requirement counts as passed here only after current evidence for every bound scenario and authority has been published; none has been published yet.

See the public verification overview and the documentation coverage guide.

Denials and recovery

If the export is refused, incomplete or unverifiable, do not replace it with a screenshot or claim a clean period. Correct the authorization or source gap and generate a fresh exact-period package.

  1. Keep the failed verdict and its scope.
  2. Ask support for non-sensitive error interpretation without sending raw content.

For customer-side next steps, read Recovery and support.

Billing and integration handoffs

A SIEM, ticket or examiner handoff is a separate recipient decision. The customer controls recipient authorization and may need its own delivery integration; a paid plan does not grant unrestricted content access.

  1. Check the selected delivery recipient.
  2. Confirm which evidence and package functions are in your current agreement.

Limits to keep in view

The current public site does not implement durable raw-content custody for evidence or holds. No private original recording or owner-library object is published in these guides, and the market workflow graph has no current passed public evidence rows.

  1. Do not use chain validity as proof of complete capture.
  2. Do not infer a current UMBRIQ customer task result from an evidence-export description.

Review the current Disclosures before relying on a capability.