OpenChainGraph Suite · CONTRACT A3 · arch #5

CSDR Penalty Recompute (Reference-Price Reachable)

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.

CSDR cash-penalty recompute using a caller-supplied reference price (ART-543) -> settlement-efficiency / penalty-cost aggregation (ART-84) -> audit receipt (cry-05). Fixes the reachability defect in the original settlement-discipline-penalty chain. Decision-support draft.

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology: CSDR Penalty Recompute (Caller Reference Price) to Settlement Efficiency KPI Engine to Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT node
per-fail penalty and forward exposure (H1), priced off a caller-supplied reference_price, feeds the KPI engine
MCP Call · recompute_csdr_penalty
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "recompute_csdr_penalty",
    "arguments": {}
  },
  "id": 1
}
↓
2 D2 node
Settlement Efficiency KPI Engine art-84-settlement-efficiency-kpi
penalty-cost rollup + efficiency score (H2) feeds the aggregator
MCP Call · compute_settlement_efficiency_kpi
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_settlement_efficiency_kpi",
    "arguments": {}
  },
  "id": 1
}
↓
3 TERMINAL · D3 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Exports composite penalty-exposure 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
}
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 fail desk says an open fail is now 60 days old instead of three. What does the recompute price at that age?
Run the AINumbers MCP tool `run_chain` with {"chain":"settlement-discipline-penalty-v2"} and read `art-543-csdr-penalty-recompute.determinations.0.penalty_amount`.
Re-run with `inputs` for `art-543-csdr-penalty-recompute`, reusing the values that result echoed, with `open_fails` changed so the open fail fail_days goes from 3 to 60. 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/settlement-discipline-penalty-v2.html