Cat Bond Trigger Validation

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.

Linear two-step chain for catastrophe bond trigger validation and payout computation. Step 1 validates cat bond trigger terms: attachment/exhaustion geometry, pro-rata or binary payout type, and layer position (BELOW_ATTACHMENT / WITHIN_LAYER / ABOVE_EXHAUSTION). Step 2 computes the parametric trigger payout from confirmed event parameters, producing a tamper-evident anchor receipt for neutral dispute adjudication (IAIS ICP 19 / ISDA CAT bond protocols). No gate: the chain always runs both steps for full economic proof.

OpenChainGraph · 2 Steps compliance mandate · Linear Hash-Anchored §4 chain_depth:2 IAIS ICP 19 · Zero PII

Chain Stages · 2 Steps · Linear (no gate)

1 ROOT node

Cat Bond Trigger Term Validator art-252-validate-cat-bond-trigger-terms

Validates cat bond attachment/exhaustion geometry, pro-rata or binary payout type, and layer position. Computes preliminary payout fraction from event_loss. Hands off confirmed trigger parameters to parametric payout computation.

MCP Call · validate_cat_bond_trigger_terms

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_cat_bond_trigger_terms",
    "arguments": {
      "attachment_point": 100000000,
      "exhaustion_point": 200000000,
      "event_loss": 150000000,
      "principal_amount": 50000000,
      "trigger_type": "parametric",
      "payout_type": "pro_rata"
    }
  },
  "id": 1
}

↓

2 TERMINAL node

Parametric Trigger Payout Calculator art-251-compute-parametric-trigger-payout

Computes parametric trigger payout for the confirmed cat bond trigger event. Produces tamper-evident trigger receipt anchored at anchor.ainumbers.co/mcp. Terminates the cat bond validation chain.

MCP Call · compute_parametric_trigger_payout

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_parametric_trigger_payout",
    "arguments": {
      "trigger_type": "threshold",
      "index_value": 150,
      "threshold": 100,
      "coverage_amount": 50000000,
      "parametric_limit": 50000000,
      "event_id": "cat-bond-2026-001"
    }
  },
  "id": 2
}

Question: The declared index value for this parametric tranche sits near its trigger. Does the payout register a hit? Run the AINumbers MCP tool `run_chain` with {"chain":"cat-bond-trigger-validation"} and read `art-251-compute-parametric-trigger-payout.trigger_hit`. Re-run with `inputs` for `art-251-compute-parametric-trigger-payout`, reusing the values that result echoed, with `index_value` changed so index_value is 90, below the 100 trigger threshold. 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/cat-bond-trigger-validation.html

Cat Bond Trigger Validation

Ask your agent