OpenChainGraph · Digital-Asset Rails · Gated

Conditional-Relief Collateral Evidence

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.

Gated six-step chain evidencing that a payment stablecoin held under a conditional regulatory relief still qualifies as collateral: GENIUS Act reserve-attestation readiness, a MiCA reserve-disclosure check gated on whether the issuer is also an e-money-token issuer, an independently verified reserve proof, tokenized-collateral eligibility, the Basel CRE22 haircut, and the conditional-relief collateral receipt itself.

compliance_control
STEP 1
GENIUS Act Reserve Attestation Pre-Check →
attestation_readiness_determination and coverage_ratio_pct establish the payment stablecoin's GENIUS Act reserve-attestation readiness before the MiCA leg is checked.
STEP 2
Check MiCA Reserve Disclosure →
token_type, coverage, and judgment_required record whether the issuer is also a MiCA e-money-token issuer and whether that leg resolved cleanly.
GATE on /token_type: "EMT" → Reserve Proof Verifier. Default → Reserve Proof Verifier (the GENIUS Act attestation from step 1 stands regardless of MiCA classification).
STEP 3
Reserve Proof Verifier →
reserve_proof_determination and root_hash_match feed the tokenized-collateral eligibility check with an independently verified reserve and depeg-staleness record.
STEP 4
Tokenized Collateral Eligibility Checker →
dtc_status and hqla_tier feed the Basel haircut engine as the tokenized leg's eligibility tier.
STEP 5
Collateral Haircut Engine (Basel CRE22) →
collateral_adjusted_total and net_exposure feed the conditional-relief receipt as the haircut-adjusted collateral value.
STEP 6
Conditional-Relief Collateral Receipt →
all_conditions_met, applicable_capital_charge, and revocation_capital_delta are the chain output.

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: We hold tokenized collateral under a conditional no-action relief. What extra capital would a revocation of that relief add?
Run the AINumbers MCP tool `run_chain` with {"chain":"conditional-relief-collateral"} and read `art-514-conditional-relief-collateral-receipt.revocation_capital_delta`.
Re-run with `inputs` for `art-514-conditional-relief-collateral-receipt`, reusing the values that result echoed, with `position_size` changed so position_size is 20000000, four times the fixture book. 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/conditional-relief-collateral.html