OpenChainGraph Suite · CONTRACT A3 · arch #5

CBAM Import Liability & Certificate Declaration

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.
Reading mode (READINESS-BUILD): These checks can be gathered in any order; the sequence below is for convenience. The emissions figure, the default-value resolution, and the certificate/phase-out schedule assemble the components of a CBAM declaration draft; it is decision support, not a filed customs declaration.

W-A flagship. Embedded-emissions calculation (ART-69) -> default-value resolution (ART-70) -> certificate cost + free-allocation phase-out + holding/surrender schedule (ART-71). The importer-to-customs CBAM declaration lifecycle end-to-end. Decision-support draft, not a filed declaration.

OpenChainGraph · 3 Steps compliance mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — CBAM Default-Value Resolver → CBAM Embedded-Emissions Calculator → CBAM Certificate Cost & Free-Allocation Engine
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
CBAM Default-Value Resolver art-70-cbam-default-value-resolver
resolved default value + markup (H1) feeds the emissions calculator
MCP Call · resolve_cbam_default_value
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "resolve_cbam_default_value",
    "arguments": {}
  },
  "id": 1
}
↓
2 D2 node
CBAM Embedded-Emissions Calculator art-69-cbam-embedded-emissions-calculator
total embedded emissions (H2) feed the certificate-cost engine
MCP Call · calculate_cbam_embedded_emissions
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "calculate_cbam_embedded_emissions",
    "arguments": {}
  },
  "id": 1
}
↓
3 TERMINAL · D3 node
CBAM Certificate Cost & Free-Allocation Engine art-71-cbam-certificate-cost-engine
Exports composite CBAM liability artifact with execution_hash (H3), final stage
MCP Call · model_cbam_certificate_cost
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "model_cbam_certificate_cost",
    "arguments": {}
  },
  "id": 1
}
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: We import iron and steel on default emissions values while paying a carbon price at origin. What CBAM certificate cost follows?
Run the AINumbers MCP tool `run_chain` with {"chain":"cbam-liability"} and read `art-71-cbam-certificate-cost-engine.certificate_liability_eur`.
Re-run with `inputs` for `art-71-cbam-certificate-cost-engine`, reusing the values that result echoed, with `origin_carbon_price_eur_per_t` changed so no origin carbon price applies, so it is 0. 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-liability.html