Verified product truth
Feature status and known boundaries
A concise map of what this documentation treats as available today and what it deliberately does not promise.
Documented as available
| Surface | Verified implementation |
|---|---|
| Portal | Public and private tournament views; Overview/Draws/Schedule tabs; accountless verified registration; optional hosted payment; player, organization, rating, and notification surfaces |
| Manager Desktop | Default Command Center with organization-scoped setup; event and format tools; registration/check-in; seeding/draw lifecycle; released table assignment and schedule publish; live results and exceptions; audit/export/archive; narrow offline queue and replay |
| Manager Mobile | iPad-side Table mode is implemented; end-to-end QR/code pairing requires the feature-gated V2 Manager shell; secure enrollment, table-locked queue, heartbeat state, and Call operator are implemented; scoring is not |
Not promised by this guide
- Point-by-point scoring from Manager Mobile Table mode. The current Start match button is disabled.
- A distinct Coach or Parent permission tier, guardian relationship, dependent registration, or coach roster in Portal. Those are guidance personas using public or normally authorized views.
- The feature-flagged V2 Manager shell's disabled Auto-schedule, delay, Print, template, Expert, or Agent controls as released default operations.
- Every backend format or HTTP endpoint described in planning documents. This guide follows visible implemented application surfaces.
- Automatic iPad Guided Access. The operator must enable it manually.
- Guaranteed real-time data during a Reconnecting state. Confirm critical changes at the desk.
Verification basis
Content was verified on July 11, 2026 at repository commit d95a40d1. Primary evidence came from Portal routes and browser tests, Manager SwiftUI views and view models, the shared Manager package target declarations, and the canonical tournament lifecycle reference.
Because product behavior changes, verify this page again before using it as a contractual feature matrix or an event-critical release checklist.