A vote with a boundary.
Holder governance changes defined application policy and future cabinet terms, using immutable token-weighted snapshots.
Eligibility
The supported token is Token-2022. One finalized getProgramAccounts response supplies the complete snapshot. All supported token accounts are summed by their on-curve owner authority. Frozen accounts, delegated token accounts, zero balances and off-curve program authorities are excluded. An RPC consistency guarantee must be configured before elections can open.
Weight stays fixed
Tokens moved after a snapshot do not create new voting weight for that election. Each eligible owner can cast one ballot. Signatures bind the domain, network, action, republic, election, choice, nonce and expiry. One wallet is not one person; this is not a claim of Sybil resistance. Voting delegation is not supported.
Results and enactment
Default turnout quorum is 20% of eligible supply. Abstentions count toward participation but not candidate totals. The uniquely highest supported option wins after quorum. Ties and no-quorum votes make no change. Votes remain open for at least 24 hours, followed by the constitutional enactment delay. Unavailable elected models pause enactment. Existing proposals with a changed term or constitution must be replaced and voted on again.
Things a vote cannot do
A vote cannot redirect creator fees, reveal keys, transfer custody, give a model arbitrary tools or raise hard operator ceilings. Expired cabinet terms retain their recorded history. No replacement is silently selected when a term or model is unavailable.