OpenChainGraph Suite · CONTRACT A3 · arch #5

CBAM Precursor Emissions Roll-Up

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.

Precursor embedded-emissions aggregation incl. the 2028 scrap rule (ART-72) -> consignment embedded-emissions calculation (ART-69) -> Merkle integrity over the supplier data set (cry-04). Lets a complex-goods producer supply verifiable embedded emissions to its importer; pre-positions the downstream-180 scope extension.

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — CBAM Precursor-Emissions Aggregator → CBAM Embedded-Emissions Calculator → Merkle Batch Verifier
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
CBAM Precursor-Emissions Aggregator art-72-cbam-precursor-emissions-aggregator
cumulative precursor SEE (H1) feeds the emissions calculator
MCP Call · aggregate_cbam_precursor_emissions
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_cbam_precursor_emissions",
    "arguments": {}
  },
  "id": 1
}
↓
2 D2 node
CBAM Embedded-Emissions Calculator art-69-cbam-embedded-emissions-calculator
consignment embedded emissions (H2) feed the verifier
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
Merkle Batch Verifier cry-04-merkle-batch-verifier
Exports composite precursor artifact with Merkle-root execution_hash (H3), final stage
MCP Call · verify_merkle_batch
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_merkle_batch",
    "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: No precursor data was supplied for these complex goods. What does the roll-up compute once one precursor is declared?
Run the AINumbers MCP tool `run_chain` with {"chain":"cbam-precursor"} and read `art-72-cbam-precursor-emissions-aggregator.cumulative_see_tco2e`.
Re-run with `inputs` for `art-72-cbam-precursor-emissions-aggregator`, reusing the values that result echoed, with `precursors` changed so one precursor at mass_fraction 0.6 with see_tco2e_per_t 2.1. 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-precursor.html