OpenChainGraph Suite · CONTRACT A3 · arch #5

Cleared Repo Collateral & Substitution

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-D. HQLA eligibility for UST collateral (505) -> collateral-swap/substitution direction (515) -> 2a-7 MMF cash-investor validation (514). Collateral side of cleared repo.

OpenChainGraph · 3 Steps collateral mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — Tokenized Collateral Eligibility Checker → Collateral Swap Eligibility Validator → Tokenized Fund Collateral Validator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Live Execution

This page is the chain definition (plan). To run the chain step by step in your browser, with each step's kernel executing in-page and a composite hash over the outputs, open the live runner:

▶ Run this chain in your browser
Chain Stages · 3 Steps
1 ROOT · D0 node
Tokenized Collateral Eligibility Checker 505-tokenized-collateral-eligibility-checker
hqla_tier + haircut feed the swap validator
MCP Call · check_tokenized_collateral_eligibility
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_tokenized_collateral_eligibility",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Collateral Swap Eligibility Validator 515-collateral-swap-eligibility-validator
swap_direction verdict feeds the fund-collateral validator
MCP Call · validate_collateral_swap_eligibility
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_collateral_swap_eligibility",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL · D3 node
Tokenized Fund Collateral Validator 514-tokenized-fund-collateral-validator
Exports composite collateral artifact, final stage
MCP Call · validate_fund_collateral
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_fund_collateral",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
▶ Run this chain (live) browser · real execution · composite §4 hash
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: Our repo desk wants to post a wrapped stablecoin where the basket currently holds Treasury tokens. Will the eligibility checker still admit it?
Run the AINumbers MCP tool `run_chain` with {"chain":"treasury-clearing-collateral"} and read `505-tokenized-collateral-eligibility-checker.dtc_status`.
Re-run with `inputs` for `505-tokenized-collateral-eligibility-checker`, reusing the values that result echoed, with `asset_type` set to "stablecoin". 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/treasury-clearing-collateral.html