OpenChainGraph Suite · CONTRACT A3 · arch #5

MiCA Token & Service Scoping

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.

Disambiguation router (ART-105) classifying ART/EMT-issuer cases (delegated to the existing stablecoin-compliance/reserve chains) vs CASP-service cases (Wave-20) -> audit receipt (cry-05). Prevents overlap; packages the MiCA suite.

OpenChainGraph · 2 Steps cryptographic mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology — MiCA Token & Service Scoper → Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT · D0 node
MiCA Token & Service Scoper art-105-mica-token-service-scoper
route decision + cross-references (H1) feed the aggregator
MCP Call · scope_mica_token_and_service
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "scope_mica_token_and_service",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL · D2 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Exports composite scoping 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
}
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: We are about to issue a payment token in the EU. Which MiCA route does the scoper assign when the token is an EMT?
Run the AINumbers MCP tool `run_chain` with {"chain":"mica-token-scoping"} and read `art-105-mica-token-service-scoper.classification`.
Re-run with `inputs` for `art-105-mica-token-service-scoper`, reusing the values that result echoed, with `inputs` changed so the token is an EMT and the activity is issuance. 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/mica-token-scoping.html