Verify Offline

Evidence integrity verification using standard tools. No proprietary software required.

Download Sample Evidence Pack

The sample Evidence Pack contains synthetic decision records in JSONL format, a SHA-256 manifest, and a POSIX shell verification script.

Evidence Pack (.jsonl) Manifest (.json) Verifier Script (.sh) OpenAPI Spec (.yaml)

Verification Steps

Step 1 — Download all files

Place all four files in the same directory.

Step 2 — Compute SHA-256 hash

On any POSIX system (macOS, Linux):

shasum -a 256 sample-evidence-pack.jsonl

Step 3 — Compare with manifest

Open manifest.json and verify the SHA-256 hash matches.

Step 4 — Or use the verifier script

chmod +x verify.sh
./verify.sh .

The script checks all files against the manifest and reports PASS/FAIL for each.

Limitations

Synthetic data. The sample pack contains fabricated decision records for demonstration purposes only.
Proof ≠ truth. Integrity verification confirms that data has not been tampered with. It does not validate the truth of the original inputs.
Demonstration boundary. This is not a production Evidence Pack. Production packs are generated by OmegaOS™ Kernel during live decision resolution.

How Production Evidence Packs Work

In production, every decision resolved by OmegaOS™ Kernel produces a signed Evidence Pack containing the decision input, policy version, evaluation trace, trilean outcome, and a SHA-256 chain linking it to the append-only Decision Evidence Log (DEL).

These packs can be exported, archived, and verified independently of the runtime — satisfying audit trail requirements under EU AI Act Art. 12 and DORA Art. 11.

Full Architecture →