Post Oak Labs · OpenChainGraph v0.3 · Educational Tool

Build a chain. See the wiring.

Click tools from the palette to compose a multi-step compliance workflow. Watch parent_hash links auto-populate in real artifacts. Then switch to Compare mode to see exactly what this replaces in the legacy world.

📚 A learning tool for students, educators, and newcomers. It teaches how chains and provenance wire together and does not execute anything. Ready to actually run a chain? Open the Workbench or the Canvas.

For students & educators Click to compose Live parent_hash wiring DAG visualization Legacy vs OCG comparison Zero egress · WebCrypto

Scenario

Basel III internal capital adequacy tools from the live catalog: VaR, stress, liquidity, credit, RWA, and regulatory reporting nodes.

AML/CTF tools from the live catalog: transaction screening, SAR/CTR, layering typology, and program-gap nodes.

Fraud and incident tools from the live catalog: customer risk, anomaly detection, and DORA incident nodes.

Every live node in chaingraph.json. Use this tab when a tool does not fit one of the three scenario buckets above.

How this works

Click a tool to add it to the chain. Each artifact records its parents' execution_hash, so every node is cryptographically linked to the outputs that drove it. Grayed tools unlock once their dependencies are present. Tools are drawn live from chaingraph.json, the real catalog, not a fixed demo set.

Available tools: click to add

Dependency guide

Tools unlock in order. Each tool records its parents' execution hashes — forming the tamper-evident DAG.

⬡

Chain is empty

Start with VaR / FRTB IMA — it's the only tool available until you have a risk baseline. Subsequent tools unlock as you add dependencies.

Suggested path

VaR → Stress Test → LCR/NSFR → Credit → RWA → Report

These are teaching artifacts over synthetic data. They are not §21 composite chain receipts; open the composed chain in Workbench or Canvas to produce one.

Artifact JSON — click a node to inspect

Click any node in the DAG above to see its full OCG v0.3 artifact, including the parent_hashes array that creates the chain link.

These are teaching artifacts over synthetic data. They are not §21 composite chain receipts; open the composed chain in Workbench or Canvas to produce one.

Same compliance audit. Two worlds. Below is the Basel ICAAP audit trail — one of the most intensive regulatory workflows in banking — as it exists today versus how it looks under OpenChainGraph. Each scenario below is a real workflow pattern drawn from Basel III/IV ICAAP submissions.

📂

Legacy process

Today — email, PDF, shared drives

⛓

With OpenChainGraph

Hash-linked, verifiable, machine-readable

Audit outcome — legacy

Audit outcome — OCG

Why verifiability matters at audit time

In a legacy audit, a regulator receives a PDF that says "our VaR is $2.85M." To challenge it, they must request the underlying model, the input data, and the calculation methodology — three separate documents, often in three different departments. Under OCG, the execution_hash is a single identifier that simultaneously proves the inputs, the computation, and the output haven't been altered. The auditor runs one SHA-256 check, in their own browser, against the artifact. No document requests, no email chains, no version confusion.