OpenChainGraph Suite · CONTRACT A3 · arch #5

EU Taxonomy Activity Alignment

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.

Activity-level Taxonomy alignment: substantial-contribution + DNSH + minimum-safeguards scoring (ART-73) -> audit receipt (cry-05). The activity-by-activity alignment decision an undertaking emits and an auditor re-verifies.

OpenChainGraph · 2 Steps cryptographic mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology — EU Taxonomy Alignment Scorer → Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT · D0 node
EU Taxonomy Alignment Scorer art-73-taxonomy-alignment-scorer
alignment verdict + gaps (H1) feed the aggregator
MCP Call · score_taxonomy_alignment
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "score_taxonomy_alignment",
    "arguments": {}
  },
  "id": 1
}
↓
2 TERMINAL · D2 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Exports composite alignment artifact with execution_hash (H2), final stage
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "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 sustainability team calls this activity taxonomy aligned. Do its criteria evidence and safeguards hold up?
Run the AINumbers MCP tool `run_chain` with {"chain":"taxonomy-align"} and read `art-73-taxonomy-alignment-scorer.alignment_verdict`.
Re-run with `inputs` for `art-73-taxonomy-alignment-scorer`, reusing the values that result echoed, with `substantial_contribution` changed so substantial_contribution set to met, with minimum_safeguards in-place. 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/taxonomy-align.html