RDARR Management-Body Attestation Cycle

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. The recomputed figure and the quality-metric scores are two separately gated checks assembled into one attestation bundle for release.

Two-step attestation cycle for risk data aggregation and risk reporting. The attestation is the deliverable: step 1 re-derives a stated risk-report figure from a declared tabular extract under a declared aggregation policy, so the signature is backed by a recomputed number rather than a self-assessment; step 2 scores the deterministic quality metrics against policy-supplied thresholds, each labelled with its ECB Guide prerequisite area. Step 1 is gated review_required when any source line is excluded from the recompute, with the risk-data owner as reviewer. Step 2 is gated dual_control(2) for periodic attestation release, with one of the two distinct approver identities bound to a management-body role. The recompute is evidence for the institution's own internal attestation; it is not a supervisory submission and carries no supervisory pass mark.

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

Chain Stages · 2 Steps

1 ROOT node review_required

RDARR Aggregation Recompute art-480-rdarr-aggregation-recompute

Recomputed figure, signed delta against the reported figure, and the per-level contribution breakdown localise a break to one roll-up node; the same extract feeds the quality scorecard

§27 Human Accountability gate: any source line excluded from the recompute routes the cycle to review_required, with the risk-data owner as reviewer, before the scorecard stage is treated as settled.

MCP Call · rdarr_aggregation_recompute

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

↓

2 TERMINAL node dual_control(2)

RDARR Quality Scorecard art-481-rdarr-quality-scorecard

Per-metric pass/breach plus an overall scorecard status, each metric labelled by ECB Guide prerequisite area, released under dual control into the accountability evidence bundle for the cycle. Final stage.

§27 Human Accountability gate: releasing the periodic attestation is dual_control(2): two distinct approver identities, one of them bound to a management-body role. A scorecard status of breach stops the cycle before release.

MCP Call · rdarr_quality_scorecard

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

Question: Before management signs the attestation, does the reported risk-aggregation figure recompute cleanly from the extract we hold? Run the AINumbers MCP tool `run_chain` with {"chain":"rdarr-attestation-cycle"} and read `art-480-rdarr-aggregation-recompute.delta`. Re-run with `inputs` for `art-480-rdarr-aggregation-recompute`, reusing the values that result echoed, with `reported_figure` set to 4999. 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/rdarr-attestation-cycle.html

RDARR Management-Body Attestation Cycle

Ask your agent