[Feat]: Short-run governance track and operator management for reservations

Component

Other

Priority

P0

Summary

Approvals of pre-launch claims run on a short governance track with a decision period under a day, since a full-length referendum per name does not fit a one-day vetting window. Operators handle day-to-day approve and revoke; OpenGov appoints and removes them and can override. Part of #202.

Proposal

• Define the short-run track: its origin, decision period, and who may decide. Standing this track up is a governance action, separate from the per-claim approvals that run on it.
• Operator role: keep multiple holders (today WHITELIST_OPERATOR_ROLE). Their remit changes from minting to approving and revoking reservations in the new contract. OpenGov grants and revokes the role and can revoke any reservation directly.
• Document how a claim moves from submitted to approved or revoked, and who signs each step.

Acceptance criteria

• The short-run track is specified: origin, decision period, deciding body.
• Multiple operators can approve and revoke; OpenGov can appoint, remove and override.
• The end-to-end approval flow is documented.
• The split between the operator fast path and OpenGov authority is written down.

Start with issue #202 and the new contract's current WHITELIST_OPERATOR_ROLE behavior. Define the short-run track's origin, decision period, and deciding body, then document the submitted-to-approved or revoked flow, including operator actions and OpenGov appointment, removal, and override authority.