Tempo Subscription & Streaming Settlement Reconciliation

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 (RUNBOOK): Run these steps in order. The reconciliation step checks draws against the cap the mandate-decoding step just extracted, so decoding the mandate has to run first.

Reconcile executed MPP recurring/streamed draws against the authorized mandate envelope, prove draw-set integrity, and aggregate receipts.

OpenChainGraph · 4 Steps settlement mandate Hash-Anchored §4 chain_depth:4 Client-Side · Zero PII

Chain Stages · 4 Steps

1 ROOT · D0 node

Tempo MPP Agent Mandate art-36-tempo-mpp-agent-mandate

granted session/subscription envelope (cap, cadence, valid_until) feeds Stage 2 reconciliation

MCP Call · decode_mpp_session

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "decode_mpp_session",
    "arguments": {}
  },
  "id": 1
}

↓

2 D2 node

Tempo Subscription Reconciler art-106-tempo-subscription-reconciler

per-cycle conformance, breaches, draw_merkle_root feed Stage 3 batch integrity

MCP Call · reconcile_mpp_subscription

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "reconcile_mpp_subscription",
    "arguments": {}
  },
  "id": 1
}

↓

3 D3 node

Merkle Batch Verifier cry-04-merkle-batch-verifier

verified draw-set Merkle root feeds Stage 4 receipt aggregation

MCP Call · verify_merkle_batch

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_merkle_batch",
    "arguments": {}
  },
  "id": 1
}

↓

4 TERMINAL · D4 node

Agent Action Audit Trail Aggregator cry-05-agent-action-audit-trail-aggregator

Exports composite subscription-settlement artifact with execution_hash — final stage

MCP Call · aggregate_execution_receipts

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "arguments": {}
  },
  "id": 1
}

Question: A subscription agent drew three monthly payments against its granted envelope. Did every draw stay inside the per-cycle and total caps? Run the AINumbers MCP tool `run_chain` with {"chain":"tempo-subscription-settlement"} and read `art-106-tempo-subscription-reconciler.verdict`. Re-run with `inputs` for `art-106-tempo-subscription-reconciler`, reusing the values that result echoed, with `envelope` changed so cap_per_cycle is 80 instead of 100. 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/tempo-subscription-settlement.html

Tempo Subscription & Streaming Settlement Reconciliation

Ask your agent