Robinhood Chain BoLD Finality Classification

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.

Gated two-step chain classifying settlement finality on Robinhood Chain. Step 1 classifies the underlying settlement-asset finality, step 2 classifies the BoLD challenge-window state. Gate on claim_verdict: overstated routes to a false-finality-claim flag, default proceeds to the finality class record.

settlement_finality_mandate

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 bridge dashboard shows a settlement as final. Is the BoLD challenge window expired for that assertion?
Run the AINumbers MCP tool `run_chain` with {"chain":"rhc-bold-finality-classification"} and read `art-321-rhc-bold-finality-classifier.finality_class`.
Re-run with `inputs` for `art-321-rhc-bold-finality-classifier`, reusing the values that result echoed, with `current_time` set to 600000. 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/rhc-bold-finality-classification.html