Single-node D0 diagnostic scoping a firm's screening/export-control program and routing to the right Wave-19 sanc-*/ec-* chain. Config-only, no customer data.
run_sanctions_screening_fit{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "run_sanctions_screening_fit",
"arguments": {}
},
"id": 1
}
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: An examiner asks how our screening program scores today. Which single control lifts the ownership dimension from zero?
Run the AINumbers MCP tool `run_chain` with {"chain":"sanctions-fit"} and read `art-90-sanctions-screening-fit-diagnostic.dim_scores.ownership_50pct`.
Re-run with `inputs` for `art-90-sanctions-screening-fit-diagnostic`, reusing the values that result echoed, with `ownership_screening` set to "50pct-aware". 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/sanctions-fit.html