Single-node D0 diagnostic classifying which carbon/climate obligations bind a firm (CBAM authorised-declarant duty, EU Taxonomy alignment, EU Green Bond conformance, climate stress) and routing to the right Wave-16 cbm-* chain; separates in-force CBAM liability (since 1 Jan 2026) from prepare-ahead items.
run_carbon_compliance_fit{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "run_carbon_compliance_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: Our CBAM goods imports passed the annual tonnage threshold. Does the fit check flag an authorised-declarant obligation?
Run the AINumbers MCP tool `run_chain` with {"chain":"cbam-fit"} and read `art-68-carbon-compliance-fit-diagnostic.cbam_declarant_required`.
Re-run with `inputs` for `art-68-carbon-compliance-fit-diagnostic`, reusing the values that result echoed, with `imports_cbam_goods` set to "above-50t". 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/cbam-fit.html