OpenChainGraph Suite · Tax & Transfer Pricing

CbCR Annual Publish

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.

OECD BEPS Action 13 Country-by-Country Report build with internal consistency gates and anomaly-pattern surfacing in one artifact. gate_status and anomaly_flags are recorded per the §27 Human Accountability vocabulary; a PUBLIC release additionally requires a dual_control(2) preparer/tax-officer gate before disclosure; both recorded now, enforced once HA-RETRO-1 wires runtime gating. Never a filed submission.

OpenChainGraph · 1 Step compliance mandate Hash-Anchored §4 chain_depth:1 Client-Side · Zero PII
Chain Topology: CbCR Annual Publish
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step
1 ROOT · TERMINAL node
OECD Country-by-Country Report Builder art-472-cbcr-builder
Builds the CbCR XML schema skeleton, runs consistency checks, surfaces anomaly_flags, and computes gate_status, final stage. PUBLIC export_mode release requires a dual_control(2) preparer + tax-officer sign-off (recorded, not yet runtime-gated) and review_required routing on any anomaly_flags before disclosure.
MCP Call · build_cbcr_report
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "build_cbcr_report",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
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: Finance assembled the country-by-country tables for the annual filing. Do any jurisdiction rows fail the consistency edits?
Run the AINumbers MCP tool `run_chain` with {"chain":"cbcr-annual-publish"} and read `art-472-cbcr-builder.fatal_failure_count`.
Re-run with `inputs` for `art-472-cbcr-builder`, reusing the values that result echoed, with `table1_jurisdictions` changed so related_party_revenue is 1200 while total_revenue stays 1000. 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/cbcr-annual-publish.html