OpenChainGraph Suite · CONTRACT A3 · arch #5

PQC Migration Audit Pack

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

W-G convergence terminal. Merkle integrity over the PQC protocol decision set (cry-04) -> Merkle-root audit receipt (cry-05) -> regulator/board-framed cover memo (ptg-01). The existing pqc-migration chain and the Wave-18 protocol chains feed in.

OpenChainGraph · 3 Steps prompt template Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — Merkle Batch Verifier → Agent-Action Audit-Trail Aggregator → AP2 Prompt Template Generator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
Merkle Batch Verifier cry-04-merkle-batch-verifier
batch integrity over PQC protocol artifacts (H1) feeds the aggregator
MCP Call · verify_merkle_batch
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_merkle_batch",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Merkle-root receipt (H2) feeds the memo generator
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL · D3 node
AP2 Prompt Template Generator ptg-01-ap2-prompt-template-generator
Exports composite PQC audit pack with Merkle-root execution_hash (H3), final stage
MCP Call · compose_ap2_prompt
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compose_ap2_prompt",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: Before this evidence pack goes to the regulator, does every proof entry in the batch verify against the declared merkle root?
Run the AINumbers MCP tool `run_chain` with {"chain":"pqc-audit-pack"} and read `cry-04-merkle-batch-verifier.batch_integrity`.
Re-run with `inputs` for `cry-04-merkle-batch-verifier`, reusing the values that result echoed, with `proof_entries` changed so proof_entries carries one entry whose leaf is the 64-zero root and carries no proof siblings. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/pqc-audit-pack.html