Skip to content

Requiem is the unified AI control plane repository. It contains: The Requiem kernel (engine + policy layer) The Reach CLI The full ReadyLayer web frontend (console, playground, enterprise UX) Single source of truth. Vercel builds the web app from apps/web.

License

Notifications You must be signed in to change notification settings

Hardonian/Requiem

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

215 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Requiem

License: MIT CI Node Determinism

Every AI decision. Provable. Replayable. Enforced.

Requiem is the Provable AI Runtime — the only execution layer where every AI decision produces a cryptographic proof, every outcome is replayable to the byte, and every policy violation is caught before it ships.

Not a prompt router. Not a workflow engine. Not a Git wrapper.

A runtime that proves what your AI actually did.


Three Guarantees

Guarantee What it means How it works
Provable Execution Identical inputs produce identical result_digest values across runs, workers, and time. BLAKE3 domain-separated hashing, canonical JSON serialization, environment sanitization. 200x repeat verification in CI.
Enforced Governance Every tool invocation passes through a policy gate. No exceptions. No bypass. Deny-by-default. Four-layer defense: RBAC capabilities, budget enforcement, content guardrails, audit logging. All enforced before execution.
Replayable Outcomes Any execution can be replayed and verified against its original proof. Divergence is detected, not hidden. Content-addressable storage with dual-hash verification (BLAKE3 + SHA-256), immutable replay logs, Merkle chain tamper evidence.

Quickstart (3 commands)

# 1. Clone and install
git clone https://github.com/Hardonian/Requiem.git && cd Requiem && pnpm install

# 2. Build the native engine
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release && cmake --build build -j

# 3. Prove determinism — runs the same workload 3x and verifies all result_digests match
./build/requiem demo

Expected output:

{"ok":true,"deterministic":true,"runs":3,"result_digest":"<hash>","latency_ms":[...]}

Determinism is confirmed when "deterministic":true and all three runs share the same result_digest.

First Deterministic Execution (TypeScript Control Plane)

# Run a tool through the policy gate and get a verifiable execution envelope
pnpm exec reach run system.echo "Hello, Determinism!"

Output:

┌─────────────────────────────────────────────────────────────┐
│ EXECUTION COMPLETE                                          │
├─────────────────────────────────────────────────────────────┤
│ Tool:          system.echo@1.0.0                            │
│ Tenant:        cli-tenant                                   │
│ Duration:      12ms                                         │
│ Deterministic: YES                                          │
│ Policy:        ENFORCED                                     │
│ Fingerprint:   a1b2c3d4e5f6...                              │
│ Replay:        VERIFIED                                     │
└─────────────────────────────────────────────────────────────┘

Verify an Execution

pnpm exec reach verify <execution-hash>

Replay with Proof

./build/requiem exec replay \
  --request docs/examples/exec_request_smoke.json \
  --result build/result.json \
  --cas .requiem/cas/v2

Inspect Policy Enforcement

# View every active constraint — nothing is implicit
./build/requiem policy explain

# View every version constant CI verifies
./build/requiem version

Launch Dashboard

pnpm exec reach ui

Microfracture Suite — Proof Surfaces

The Microfracture Suite provides deterministic analysis, comparison, and verification tools for AI executions.

10-Minute Proof Flow

# 1. Run a tool
reach run system.echo "Hello, World!"
# → Returns run ID: run_abc123...

# 2. Run it again
reach run system.echo "Hello, World!"
# → Returns run ID: run_def456...

# 3. Diff the runs
reach diff run_abc123 run_def456 --format=table
# → Shows deterministic comparison

# 4. Create a shareable proof card
reach diff run_abc123 run_def456 --share
# → Prints share URL for /proof/diff/<token>

# 5. Verify lineage
reach lineage run_abc123 --depth=5
# → Shows parent/child relationships

# 6. Check tenant isolation
reach tenant-check --format=table
# → Verifies no cross-tenant data leakage

CLI Commands

Command Purpose Example
reach diff <A> <B> Deterministic run comparison reach diff run1 run2 --card
reach lineage <id> Show run ancestry reach lineage run1 --depth=10
reach simulate <id> Test policy evaluation reach simulate run1 --policy=strict
reach drift --since=<id> Detect behavior changes reach drift --since=run1 --window=50
reach explain <id> Generate run explanation reach explain run1 --format=md
reach share <id> Create shareable proof link reach share run1 --ttl=48h
reach usage Show tenant usage summary reach usage --format=json
reach tenant-check Verify isolation boundaries reach tenant-check
reach chaos --quick Run verification checks reach chaos --quick

Diff Proof Card

The Diff Proof Card is a screenshot-worthy artifact showing:

  • Run A + Run B IDs (shortened)
  • Tenant scope indicator
  • Determinism VERIFIED badge
  • Replay Match percentages
  • Fingerprint summaries (with copy buttons)
  • Top 3 deltas (input/output/policy/graph)
  • First divergence point
  • "Verified by Requiem" footer with timestamp

Access via:

  • CLI: reach diff <A> <B> --card → prints local URL
  • CLI: reach diff <A> <B> --share → creates share token
  • Web: /proof/diff/<token> → public share route
  • Web: /runs/<id>/diff?with=<id>&card=1 → internal view

Exit Codes

All commands follow standard exit codes:

  • 0 — Success / Determinism verified
  • 2 — User error (invalid arguments, missing run)
  • 3 — Invariant failure (determinism mismatch, tenant violation)
  • 4 — System error (database, network)

Web UI Routes

Route Purpose
/runs/[runId] Run detail with Proof Panel
/runs/[runId]/diff?with=[runId] Diff comparison view
/runs/[runId]/lineage Lineage DAG visualization
/runs/[runId]/drift Drift timeline
/runs/[runId]/simulate Policy simulation results
/shares Share link management
/usage Usage dashboard
/tenant-check Tenant audit report
/chaos Chaos check results
/proof/diff/[token] Public proof card (shareable)

Two CLIs: ./build/requiem (C++ native engine — determinism, CAS, replay, policy) and pnpm exec reach (TypeScript control plane — AI decisions, junctions, MCP). See CLI Reference.


Architecture

┌─────────────────────────────────────────────────────────┐
│                    Dashboard (Next.js)                    │
│         Executions · Replay · Audit · Metrics            │
├─────────────────────────────────────────────────────────┤
│                  Control Plane (TypeScript)               │
│     Policy Gate · Tool Registry · MCP · Skills           │
├─────────────────────────────────────────────────────────┤
│                  Native Engine (C++)                      │
│   BLAKE3 Hashing · CAS v2 · Sandbox · Replay Verify     │
├─────────────────────────────────────────────────────────┤
│                  Formal Verification                     │
│        TLA+ Specs · Model Checker · Chaos Harness        │
└─────────────────────────────────────────────────────────┘

Every layer enforces the same invariants. Claims are verified in code, not implied in copy.


Why Enterprises Switch

Problem Without Requiem With Requiem
"Did the AI do the same thing twice?" Hope so Prove it — result_digest match
"Can we audit what happened?" Grep through logs Immutable Merkle chain with replay proof
"Is policy being enforced?" Trust the wrapper Deny-by-default gate — every invocation, no bypass
"Can we reproduce this in court?" No Replayable to the byte, with cryptographic evidence

Why Builders Prefer It

  • 10-second proof: Run a tool, get a hash, verify it. Determinism is visible, not promised.
  • No hidden steps: policy explain shows every active constraint. Nothing is implicit.
  • Replay is not logging: Replay re-executes and verifies. Divergence is detected, not ignored.
  • Policy is not middleware: It's a gate. Deny-by-default. No tool executes without passing.

Tiers

OSS Pro Enterprise
Deterministic execution Yes Yes Yes
CAS with dual-hash verification Yes Yes Yes
Policy gate (deny-by-default) Yes Yes Yes
Replay verification Yes Yes Yes
CLI + Dashboard Yes Yes Yes
Execution credits / month 1,000 50,000 Unlimited
Replay storage 1 GB 50 GB Unlimited
Policy events tracked 10,000 500,000 Unlimited
Multi-tenant isolation Yes Yes
SOC 2 compliance controls Yes
Signed artifact chain Yes
Cluster coordination Yes
SLA-backed support Yes

Verification

# Fast checks (lint, typecheck, boundaries) — run before every commit
pnpm run verify

# Full CI suite including determinism and integration tests
pnpm run verify:ci

For architecture details, see Architecture Overview.

Contributing

See CONTRIBUTING.md and CODE_OF_CONDUCT.md.

License

MIT

About

Requiem is the unified AI control plane repository. It contains: The Requiem kernel (engine + policy layer) The Reach CLI The full ReadyLayer web frontend (console, playground, enterprise UX) Single source of truth. Vercel builds the web app from apps/web.

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors