OpenChainGraph Suite · CONTRACT A3 · arch #5

EU Green Bond Factsheet & Allocation Conformance

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.

EuGB factsheet (Annex I) + allocation report (Annex II) completeness + proceeds-alignment validation (ART-75) -> use-of-proceeds Taxonomy alignment cross-check (ART-73) -> Merkle integrity over the bond evidence set (cry-04). The issuer-to-external-reviewer green-bond conformance pack. Decision-support draft, not a reviewer attestation.

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — EU Green Bond Factsheet & Allocation Validator → EU Taxonomy Alignment Scorer → Merkle Batch Verifier
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
EU Green Bond Factsheet & Allocation Validator art-75-eugb-factsheet-validator
factsheet/allocation conformance + proceeds-aligned % (H1) feeds the alignment scorer
MCP Call · validate_eugb_factsheet
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_eugb_factsheet",
    "arguments": {}
  },
  "id": 1
}
↓
2 D2 node
EU Taxonomy Alignment Scorer art-73-taxonomy-alignment-scorer
use-of-proceeds alignment (H2) feeds the verifier
MCP Call · score_taxonomy_alignment
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "score_taxonomy_alignment",
    "arguments": {}
  },
  "id": 1
}
↓
3 TERMINAL · D3 node
Merkle Batch Verifier cry-04-merkle-batch-verifier
Exports composite EuGB conformance 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: The allocation report landed this morning. With it on file, does the Annex II leg of our European green bond pack finally read complete?
Run the AINumbers MCP tool `run_chain` with {"chain":"eugb-conformance"} and read `art-75-eugb-factsheet-validator.annex_ii_status`.
Re-run with `inputs` for `art-75-eugb-factsheet-validator`, reusing the values that result echoed, with `allocation_report` set to "complete". 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/eugb-conformance.html