OpenChainGraph Suite · CONTRACT A3 · arch #5

CASP Authorization & Own-Funds

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.
Reading mode (READINESS-BUILD): These checks can be gathered in any order; the sequence below is for convenience. Authorization readiness and the own-funds calculation are combined into one licensing readiness draft; it is decision support, not an executed licensing filing.

W-A flagship. CASP authorization-readiness (governance, custody segregation, conflicts) (ART-100) -> Art 67 own-funds calculation (ART-101) -> audit receipt (cry-05). The CASP licensing lifecycle end-to-end. Decision-support draft.

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — CASP Authorization-Readiness Assessor → Art 67 Own-Funds Calculator → Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
CASP Authorization-Readiness Assessor art-100-mica-casp-authorization-readiness
authorization grade + gaps (H1) feed the own-funds calculator
MCP Call · assess_mica_casp_readiness
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "assess_mica_casp_readiness",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Art 67 Own-Funds Calculator art-101-mica-art67-own-funds-calculator
own-funds requirement (H2) feeds the aggregator
MCP Call · calculate_mica_own_funds
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "calculate_mica_own_funds",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL · D3 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Exports composite authorization artifact with execution_hash (H3), 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: Budget season. How much own capital must the CASP hold, and which leg of Article 67 binds?
Run the AINumbers MCP tool `run_chain` with {"chain":"mica-casp-authorization"} and read `art-101-mica-art67-own-funds-calculator.required_own_funds`.
Re-run with `inputs` for `art-101-mica-art67-own-funds-calculator`, reusing the values that result echoed, with `fixed_overheads_annual` set to 400000. 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-casp-authorization.html