A commissioner with configured capability operating the owning league instance.
Dynasty/redraft; HQ is bounded read-only portfolio and links to owning league for writes. Published playoff truth is member-visible; preview is commissioner-only.
HELP TOPIC // commissioner
/commissioner-operations · corpus 0.1 · verified 43c1c50
Commissioner operations
Run a league intentionally: admission, setup, draft control, weekly processing, playoff truth, recovery, and isolated HQ.
Sources
Who can use this answer.
Read the current gate
Commissioner authorization, current league identity, and a read of state before every mutation.
The label carries the consequence.
Ready, not-ready, scheduled, running, paused, stale, degraded, unavailable, failed, final, preview-only, published, waiting-for-ledger, corrected, recovery-required.
Use the runtime clock
Draft, waiver, trade, lineup, close, playoff, and notification deadlines come from runtime configuration.
Keep the right audience
HQ summaries and public bracket projections are PII-free and do not merge sessions or expose addresses.
Take the next safe step.
- →
Verify identity, seats, order, schedule, readiness, source health, and postseason provenance.
- →
Use typed confirmations for destructive/force/publish/correction actions.
- →
Read persisted result, bracket truth, and activity receipt.
- →
Advance playoffs only from complete final authoritative ledgers; never enter scores in a browser form.
- →
After restart/stale response, reconcile before retry. Earlier-round correction requires a fresh preview.
- →
Use HQ only to find attention; mutate in owning league.
Know what changes.
What happens
Start/force/undo/close/reset/release/publish/advance/correction can change durable state and name affected objects.
What can be undone
Only documented action is reversible; final/reset/publish/correction controls require confirmation/audit. A retry of the same publication is idempotent.
What you should see
Commissioner sees receipt, current persisted bracket revision, source provenance, and next operation.
Keep context. Do not replay blindly.
Stale/double/unauthorized/partial/degraded actions fail closed; peer failure is isolated.
Follow handbook normal/restart/source recovery; wait for final ledgers, retry bounded actions, or rebuild a fresh preview. Never edit SQLite.
One concrete read.
Example: A scheduled meeting remains stopped until the commissioner intentionally confirms start; a bye advances without a fabricated opponent score.
Runtime source: League state/config, postseason truth/provenance, final scoring ledger, authorization, processors, health, activity, peer summaries.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.