Immutable data release evidence packs

What the evidence pack contains

Audarel joins the release, agreement version, confirmed controls, artifact metadata and hashes, deterministic findings, every release run, attestations, approval decisions, exceptions, policy bundles, and connector bindings into one snapshot.

• Decision and decision-engine version
• Agreement and amendment version
• Schema, payload, manifest, and user-list hashes
• Source-cited controls and findings
• Approver identity, tier, mode, comment, and time
• Exception reason, remediation, owner, and status
• Desired and observed connector hashes

Human-readable PDF and machine-readable JSON

The PDF supports review, audit, and governance committees. The JSON supports re-performance, internal analytics, control testing, and downstream evidence systems. Both are derived from the same canonical snapshot and receive their own content hashes.

Immutability without obscuring change

A generated pack is never updated in place. A changed agreement, artifact, approval, exception, or connector state creates a new run and, when requested, a new evidence pack. Earlier evidence remains available so the organization can explain what it knew and decided at that time.

Evidence quality test

Give the pack to a qualified reviewer who did not participate in the original release. They should be able to identify the source authority, reproduce the material checks, distinguish automated findings from human decisions, and see whether downstream enforcement matched the approved policy.

Confirm requirements against current source material.

Requirements and vendor capabilities change. Confirm the current source and your approved QC plan before changing a production process.

• NIST SP 800-53 Rev. 5 — Audit and Accountability