MATHEMATICALLY PROVABLE AI AUDIT EVIDENCE

Zero-Trust Flight Recorder
For Autonomous Lending Decisions

Transforms mutable AI logs into post-quantum cryptographic receipts with zero critical-path latency overhead. Engineered to meet strict EU AI Act Article 19, DPDP Act, and RBI regulatory standards.

0 Evaluations Processed
0 Merkle Tree Leaves
< 2 ms Critical Path Latency
100% Air-Gapped Verifiable
01 UPSTREAM TRIGGER

Applicant Loan Portal

Simulate loan requests evaluated by algorithmic underwriting rules. Features strict EU AI Act natural person identity validation and sub-5ms client responses.

  • โœ“ Natural person identifier verification
  • โœ“ Instant prime & subprime risk tiering
  • โœ“ Automatic out-of-band audit dispatch
02 TRANSPARENCY VIEW

Live Flight Recorder Log

Real-time visual feed of the append-only RFC 6962 Merkle tree. Observe new SHA-256 leaf hashes sealed out-of-band without customer latency.

  • โœ“ Live Signed Tree Head (STH) root hash
  • โœ“ Real-time SHA-256 leaf hash feed
  • โœ“ Fail-open signed loss entry monitoring
03 MATHEMATICAL PROOF

Auditor Verification Studio

Air-gapped 100% in-browser cryptographic verification studio. Validate the 7 Northwind Cipher domains on any receipt with zero server trust.

  • โœ“ Client-side Web Crypto SHA-256 binding
  • โœ“ Ed25519 & ML-DSA-65 post-quantum hybrid
  • โœ“ 1-Bit tamper attack detection simulator
ENGINEERING BLUEPRINT // COOL SDK ARCHITECTURE

How CooL Powers The Zero-Trust Flight Recorder

From high-speed credit underwriting to post-quantum Merkle sealing: explore the five architectural stages that transform mutable logs into legally admissible mathematical evidence under EU AI Act Article 19.

CooL SDK Zero-Trust AI Flight Recorder Pipeline
FIGURE 1.0 // NON-BLOCKING OUT-OF-BAND ARCHITECTURAL PIPELINE (ISO/IEC 42001 & EU AI ACT)
5 CORE TENETS

The CooL SDK Architectural Philosophy

01
Never Sit in the Critical Path

The capture hook fires asynchronously into an in-memory ring buffer. Borrowers receive loan decisions in < 2ms with fail-open signed loss safety.

02
Sensitive Data Stays in Customer Boundary

Raw PII, financial histories, and credit scores never cross external boundaries. Only deterministic cryptographic hashes are appended to the transparency log.

03
Deterministic Canonical Serialization

RFC 8949 Canonical CBOR enforces exact byte agreement across diverse hardware architectures, eliminating hash mismatch ambiguities.

04
Hybrid Post-Quantum Cryptography

Dual signatures pair classical Ed25519 (64-byte speed) with NIST FIPS 204 ML-DSA-65 (3,309-byte lattice security) to guarantee a 10-year regulatory retention horizon.

05
RFC 6962 Merkle Transparency Tree

Cryptographic append-only logs prove inclusion with O(log n) audit paths and prevent retroactive history rewriting through Signed Tree Heads (STH).

STEP-BY-STEP EXECUTION

Cryptographic Lifecycle of an Autonomous Credit Decision

STAGE 01

Ingestion & Article 19 Guard

Borrower submits credit application. The API validates natural person identities, rejecting machine tokens (svc:*, client:*) under EU AI Act Article 19, and executes underwriting rules in < 2ms.

โ†’
STAGE 02

Out-of-Band Capture Hook

The CooL gateway hook intercepts the decision asynchronously into a bounded queue. Fails open on extreme load, logging signed loss entries with zero dropped loans.

โ†’
STAGE 03

Canonical CBOR & SHA-256

Background sealer encodes the decision data into deterministic RFC 8949 CBOR bytes and computes a 256-bit binding digest that catches any 1-bit tampering.

โ†’
STAGE 04

Hybrid Post-Quantum Sealing

The record is signed simultaneously with classical Ed25519 and post-quantum ML-DSA-65 (NIST FIPS 204), ensuring 10-year quantum resilience.

โ†’
STAGE 05

Merkle Log & Zero-Trust Audit

Appended to the RFC 6962 transparency tree. Regulators verify the 7 Domains directly in their browser with Web Crypto and test the 1-Bit Tamper Simulator.

01

Applicant Loan Evaluation

The Trigger: Algorithmic Underwriting Ingestion & Natural Person Guard

Test Presets:
Must represent a verified natural human person. Machine tokens (svc:*, client:*) are rejected.
02

Live Transparency Engine

The Transparency View: RFC 6962 Merkle Tree & Telemetry HUD

0 Evaluations
0 Approved
0 Rejected
0 Merkle Leaves
0 Loss Entries
SIGNED TREE HEAD (STH) ROOT HASH LIVE
Calculating root hash...
APPEND-ONLY LEAF HASH STREAM (SHA-256)
Awaiting loan decisions to seal in Merkle transparency log...
03

Auditor Verification Studio

The Proof: Zero-Trust 100% Client-Side 7-Domain Audit

โค“

Drop receipt.json here to verify

or click to browse local filesystem

๐Ÿงช AUDITOR SUITE: VERIFIED & UNVERIFIED EXAMPLES
AIR-GAPPED AUDIT EXAMPLES

Select any of the 4 pre-built test cases below to simulate real-world audit scenarios directly in the browser or via CLI:

CASE 01 // PASS Fully Verified Receipt

Valid CBOR payload, matching SHA-256 digest, Ed25519 & ML-DSA-65 signatures, Merkle proof, and natural person identity.

๐Ÿ“ฅ JSON
CASE 02 // FAIL Tampered Payload Hash

Single bit flipped in the SHA-256 payload digest. Fails Domain 02 (Binding) & Domain 05 (Consistency).

๐Ÿ“ฅ JSON
CASE 03 // FAIL Invalid Ed25519 Signature

Corrupted classical digital signature bytes. Fails Domain 03 (Signature Authentication).

๐Ÿ“ฅ JSON
CASE 04 // FAIL Article 19 Identity Violation

Identity is set to machine service account (svc:automated_bot), violating EU AI Act natural person requirements.

๐Ÿ“ฅ JSON
๐Ÿ’ป AIR-GAPPED VERIFIER CLI COMMAND
# Run air-gapped verification directly from terminal:
$ python src/verifier/cli.py \
    --receipt case1_valid.json \
    --public-key akyOBbMOxps6vQpOCK5outw7+XKm+0nZtxa/cRdzrWs= \
    --root afe24a6a78a40f75b9546c20c7026277bfbcf11640e0eb7aadc44e2ae063e945

# Or output machine-readable JSON:
$ python src/verifier/cli.py --receipt case1_valid.json --json
NORTHWIND CIPHER // SEVEN VERIFICATION DOMAINS
01 Canonical WAITING

RFC 8949 CBOR deterministic serialization

02 Binding WAITING

SHA-256 payload digest match (Browser Web Crypto)

03 Signature WAITING

Ed25519 & ML-DSA-65 post-quantum hybrid signatures

04 Inclusion WAITING

RFC 6962 Merkle tree audit path validation

05 Consistency WAITING

Monotonic append-only log verification

06 Attestation SIMULATED

Hardware TEE quote status (Enclave simulation mode)

07 Witnesses ABSENT

Independent multi-party co-signers

DECODED ARTICLE 19 AUDIT RECORD UNLOADED
// Drop a receipt above or click 'Verify System Receipt' to inspect decrypted fields