OpenChainGraph · Robinhood Chain

Robinhood Chain Regime Mapping

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.

Single-step chain mapping the regulatory regime implied by a Robinhood Chain stock-token characterization, inverting the MiCA/GENIUS assumption that applies to the estate's other digital-asset-rail chains.

crypto_regulatory_mandate
STEP 1
regime_tree, mica_carveout_applies, and us_persons_gate_violated feed the regime record.

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 stock token is characterized as a debt security issued through an SPV. Does that characterization keep it outside MiCA and inside MiFID II?
Run the AINumbers MCP tool `run_chain` with {"chain":"rhc-regime-mapping"} and read `art-318-rhc-regime-mapper.mifid2_transferable_security`.
Re-run with `inputs` for `art-318-rhc-regime-mapper`, reusing the values that result echoed, with `instrument_type` set to "tokenized_equity". 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-regime-mapping.html