Four-step verify-side chain: reserve-attestation precheck, MiCA-style reserve stress simulation, partner-jurisdiction routing, and partner-stablecoin readiness score compose into a daily reserve-precheck receipt a regulator or auditor of a community bank can independently replay.
This chain is strictly the auditor/regulator verify surface (it rides the live RESERVE-WATCH cron). It does NOT build or imply an issuer-side reserve-report pre-filer or composer. The receipt asserts "these inputs replay to this readiness verdict," and never "these reserves are attested or proven." There is no claim of cryptographically verifying an underlying reserve PDF.
Each step's receipt entry carries that kernel's existing proof status honestly — this chain composes only already-shipped, already-proven kernels; there is no new groth16 proving step for this composition. The chain's claim_strength is the minimum across steps: it is replayable-by-hash, not a fresh cryptographic proof of the underlying reserves.
precheck_reserve_attestation{
"jsonrpc": "2.0",
"method": "tools/call",
"params": { "name": "precheck_reserve_attestation", "arguments": { "issuer_ref": "SYNTHETIC-ISSUER-FIUSD" } },
"id": 1
}
simulate_stablecoin_reserve{
"jsonrpc": "2.0",
"method": "tools/call",
"params": { "name": "simulate_stablecoin_reserve", "arguments": { "issuer_ref": "SYNTHETIC-ISSUER-FIUSD" } },
"id": 2
}
route_partner_stablecoin_jurisdiction{
"jsonrpc": "2.0",
"method": "tools/call",
"params": { "name": "route_partner_stablecoin_jurisdiction", "arguments": { "issuer_ref": "SYNTHETIC-ISSUER-FIUSD" } },
"id": 3
}
score_partner_stablecoin_readiness{
"jsonrpc": "2.0",
"method": "tools/call",
"params": { "name": "score_partner_stablecoin_readiness", "arguments": { "issuer_ref": "SYNTHETIC-ISSUER-FIUSD" } },
"id": 4
}