OpenChainGraph Suite · Retirement Decumulation

Retirement Decumulation Decisions

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.

Pairs the Social Security claiming-age optimizer with the pension lump-sum-vs-annuity decision engine. Figures are user-supplied off the claimant's own statement and election paperwork; no PII stored, no live feeds.

OpenChainGraph · 2 Steps compliance mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology: Retirement Decumulation Decisions
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
Social Security Claiming-Age Optimizer art-282-social-security-claiming-optimizer
recommendedClaimAge and lifetimePV establish the claimant's decumulation income baseline used alongside the pension lump-sum-vs-annuity comparison
MCP Call · optimize_social_security_claim_age
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "optimize_social_security_claim_age",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL node
Pension Lump-Sum vs. Annuity Decision Engine art-283-pension-lump-sum-vs-annuity-decision-engine
annuityPV, breakEvenRate, and recommendation form the paired decumulation decision record; terminal stage
MCP Call · compare_pension_lump_sum_annuity
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compare_pension_lump_sum_annuity",
    "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: A colleague was offered a 300000 lump sum against a 2000 monthly pension. Which is the better deal for them?
Run the AINumbers MCP tool `run_chain` with {"chain":"retirement-decumulation-decisions"} and read `art-283-pension-lump-sum-vs-annuity-decision-engine.recommendation`.
Re-run with `inputs` for `art-283-pension-lump-sum-vs-annuity-decision-engine`, reusing the values that result echoed, with `election` changed so its lumpSum offer is 700000. 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/retirement-decumulation-decisions.html