# Human Gates and Scenario Register

Candidate-Commit: `BLOCKED_NO_FINAL_SOURCE_COMMIT`

The public-address intake requires governance signers, guardian, treasury,
named partner, counsel, and auditor routes. It accepts no wallet secret,
signature, private key, or deployment authorization.

The rehearsal register contains 19 exact scenario IDs. It must contain every
ID exactly once; duplicate entries fail validation even if every expected ID is
present. The custody scenarios demonstrate typed participant mutual consent,
replay rejection, wrong-chain/wrong-bond/wrong-amount rejection, expiry and
force-exit principal refunds, and pause/recovery behavior. It also records that
generic consensus/dispute inputs and prohibited data hashes cannot affect
Base-pilot custody.

A planned scenario is not a pass. A pass requires public receipts, exact event
and state evidence, reconciliation, and independent human review after a clean
committed source/archive/artifact binding has been supplied.
