Supervisor guide
Choose the work. Follow its progress. Make the decisions only a person should make.
The review desk keeps each market tied to its exact source meaning, evidence, and revision. A supervised run can gather and check work, while gate decisions remain yours.
You do not need terminal commands. The supervisor runs routine operations and brings decisions or missing information back to this page.
First visit
Create your operator account privately
If this is a new review desk, open the one-time setup invitation supplied by the service administrator. The page will ask you to choose a username and password, then sign you in.
Enter both only in the setup page. If the invitation has expired or setup is unavailable, ask the service administrator for a fresh invitation.
Start bounded work
Select the exact markets you want handled
- Select markets in the queue.Use the checkbox beside each row. Search and filters help narrow the visible set. A single run can include up to ten markets.
- Choose Preview or Live.Preview works toward preview release and activation and omits grading. Live adds the grading gates and the live release target. The choice sets workflow scope; it does not approve a release or deployment.
- Add direction if it helps.State the result you need checked, a constraint, or relevant context. You do not need to describe implementation details.
- Select Run selected.The activity panel will show the durable run and each bounded job inside it.
If readiness says “Needs attention,” read the issue shown there. The desk will keep the run button unavailable until the supervisor can start safely.
Activity and attention
Read status as a statement of what is happening now
Work is active. The page refreshes its progress.
The supervisor has asked for missing context or a gate is ready for your decision. Reply with context in the attention box; use Review decision for approval.
A specific issue prevents progress. Read the stated issue and provide the requested input when you can. A blocked result is not supported work.
No new work should advance for this run. Select Resume when you want it to continue.
Every selected row reached the approved activation target for the chosen mode. Preview completion does not include Live or grading approval.
Use Pause when you need time to inspect the work or stop further progress. Use Resume after the reason for pausing has been addressed. When a run asks for attention, answer the specific question in the run card; your response becomes part of the supervised activity but never counts as a gate approval.
Review and decide
Judge each gate from its evidence
Open a market and compare its source observation with the proposed target. Then inspect the gate blockers, evidence receipts, screenshots, and decision history. The six gates cover distinct questions and may advance at different times.
Select Review decision on a gate to approve this version of the evidence, request evidence, defer, or reject. Explain what is missing when you request evidence, defer, or reject. If relevant data changes later, the old decision no longer applies to the updated version.
Approving a release authorizes activation of the exact release you reviewed in the intended environment. Any change to that release requires another review.
A screenshot can show that a market appeared. It cannot establish that settlement is correct. Approve each gate only from evidence that answers that gate’s question.
What to look for
Check the product shape, player-stat scope, and exact display
A ladder offers several fixed thresholds as one market shape. A generic over/under is a two-sided choice around a line. Similar words do not make them interchangeable: compare every raw selection, threshold, and label before accepting the mapping.
For example, 210+ / 230+ / 240+ passing yards must not be mapped to the same two-sided market as Under 235.5 / Over 235.5. Reject that proposed mapping even if the agent explains a mathematically equivalent threshold. For Passing + Rushing Yards, require both player statistics; team or period scores do not establish the needed data.
For player statistics, confirm the athlete, statistic definition, aggregation, game or period scope, overtime treatment, and participation rule. “Tackles,” for example, may or may not include assisted tackles depending on the source contract.
In display evidence, check the event identity, market title, every visible selection label and line, and the intended live or prematch placement. Make sure the screenshot belongs to the same execution as its trace. The screenshot alone does not prove the upstream path or grading behavior.
If a market parses but does not appear, request the first point where it was dropped or hidden. The supervisor should investigate category filters, UI allowlists, grading-availability settings and the rest of the delivery path. You should receive the finding and corrected evidence, rather than instructions to debug those systems yourself.
For example: “Provide a raw sample containing the alternate thresholds and a direct upstream-to-display trace from the same execution.”
Catalog authority
Review the schema version behind the catalog
The reviewed version of sports-schema defines the catalog. Its version and content identity must match the fresh catalog database used for the evidence. Running databases are checked copies, not independent sources of truth.
The supervisor may read the replay environment’s catalog to show what that runtime actually used. It compares that read-only result with sports-schema and reports any difference instead of silently accepting the database as authority.
If required catalog information is missing, request a reviewed sports-schema update. Do not ask for a one-off database edit. The supervisor should rebuild a fresh database from the updated schema and show that the intended environments match it.
A release approval covers the exact schema version, catalog content, and tested runtime shown in the evidence. A change to any of them requires updated evidence and another release review. Display and grading decisions remain separate.
When you are done
Leave a clear, durable outcome
A completed Preview run can still leave grading and Live release gates pending. A Live run completes only after all its required gates and activation finish. Record the decision that matches the evidence, and use the reason field to tell the next reviewer what remains. The market history preserves those actions against the exact revision.
Service owners can find installation, recovery, and boundary details in the accompanying Administration Guide.