OpenChainGraph Suite · Verify-Rails · VR-3 wave 1

Anchored Extract Verification

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.

Single-node diagnostic verifying an extract's Merkle inclusion against a root only when that root is externally anchored (RFC 3161, OpenTimestamps, Sigstore, or on-chain via VR-1) or is a recognized OCG artifact envelope. A self-produced, unanchored root is refused, not silently passed.

OpenChainGraph · 1 Step compliance mandate Hash-Anchored chain_depth:1 Client-Side · Zero PII
Chain Topology: Anchored Extract Verification
Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step
1 ROOT · TERMINAL node
Anchored Extract Verifier art-286-anchored-extract-verifier
anchored_extract_determination and escalation feed the auditor's evidence-inclusion workpaper; composes with VR-1 (verify_eth_state_proof) for the on-chain anchor class, standalone otherwise
MCP Call · verify_anchored_extract
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_anchored_extract",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the 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: A vendor sent an extract with its own Merkle root. Does the verifier accept that root, and what does it take before a mismatch escalates?
Run the AINumbers MCP tool `run_chain` with {"chain":"anchored-extract-verification"} and read `art-286-anchored-extract-verifier.anchored_extract_determination`.
Re-run with `inputs` for `art-286-anchored-extract-verifier`, reusing the values that result echoed, with `source_class` set to "ocg_artifact". 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/anchored-extract-verification.html