Verify Offline

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

Offline Verification Approach

Every Evidence Pack produced by OmegaOS™ Kernel includes a cryptographic manifest and can be verified using standard tools — no proprietary software required.

Verification tooling and sample packs are provided to pilot partners during onboarding. Contact us to request access.

Verification Process

Step 1 — Obtain your Evidence Pack

Evidence Packs are exported from OmegaOS™ Kernel during pilot or production operation. Each pack includes a cryptographic manifest.

Step 2 — Compute and compare hashes

Compute the cryptographic integrity hash of each evidence file and compare against the manifest values. Standard tools on any operating system are sufficient.

Step 3 — Independent verification

All verification uses standard cryptographic primitives (cryptographic integrity verification and digital signatures). No proprietary tooling is required.

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.

Online Verification (Public Portal)

In addition to offline verification, OmegaOS™ Kernel provides a Public Verification Portal for real-time decision integrity checks. External auditors, regulators, or counterparties can verify a specific decision without access to your systems.

  • Token-based. Each verification token is tied to a specific decision and its cryptographic inclusion proof.
  • Zero-knowledge. The verifier confirms the decision exists in the append-only ledger without seeing other decisions, internal policies, or evidence details.
  • No authentication required. The public verification endpoint does not require API keys or login — the token itself is the credential.
  • Audit-logged. Every verification attempt is recorded with timestamp, IP, and user-agent for compliance traceability.

The verification endpoint returns decision state, timestamp, integrity status, and cryptographic proof — or an error if the token is invalid or revoked.

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 cryptographic hash chain linking it to the append-only ledger.

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 →