Regular play
Play two rounds
Answer each regular question as it opens. The match page is the authority for your exact schedule and deadlines during the two-week beta window.
Beta test · Round 2
Play the whole game. Make the ending count.
Over a two-week window, you will play two regular rounds, wager on the subject of a final question, answer that question, and watch the match reach final standings. Use the dates and deadlines shown in your match; this briefing deliberately does not duplicate the live schedule.
Keep confidential work information out of answers and reports. Treat the game like a public room even though its match records are private.
The complete path
Four stages from opening clue to final score.
The final challenge has separate wager and answer windows. The site should always tell you which one is open, what is already locked, and what comes next.
Reserved wager day
Choose a private wager
The schedule reserves a wager day after regular play. Once regular scores and reviews are final, the subject appears and you can wager privately using the points available to you. If scorecards are not ready before that window closes, both final-challenge dates move together.
Reserved answer day
Answer the final question
The final question opens on the playable day after wagering and closes at the end of that published day. Submit one private answer and watch how judgement or review affects the final result where those controls are available.
Results Day
Meet the winner
On the next playable day, the match page should announce the winner or explain that scorecards are still being checked. It must not declare final standings while an answer or review can still change the score.
Where attention helps most
Follow the seams, not just the questions.
Round transitions, private final-challenge state, deadlines, retries, and hands-free preparation are the consequential paths in this test.
Progress between rounds
The next available question, catch-up order, and round labels should remain clear as the match crosses from the first round into the second.
Topic and available points
The subject should be understandable before you wager, the allowed range should match your available score, and the amount must stay private.
One answer, one outcome
The final answer should be accepted once, judged once, and applied to the score once—even if you refresh, go back, or retry after a slow response.
Natural-time deadlines
If you intentionally skip a wager or final answer, let the real deadline pass. We especially need evidence that the match advances without manual intervention.
The next game appears
For a subscribed group, the automatic series should prepare the next eligible match without creating duplicates. Group administrators should see honest blocked or retry states.
Announcements and email
Tell us whether group announcements and lifecycle email controls match what actually happened. Do not assume inbox delivery merely because the site says a send was accepted.
Known limitations
Useful context before you report.
These boundaries are expected. The public release notes remain the current record if this list changes during the round.
- This is still a beta. Natural-time automation, retry, no-answer, and finalization evidence is the point of this round, not a completed claim.
- Email acceptance and site status do not prove that a provider placed a message in an inbox. Report missing or duplicate mail directly.
- Production web and AppSync components can be deployed at different times. A copied web build identifies the site you saw, not every backing service.
- Creating billing plans, charging a card, and paid subscriptions remain outside this beta.
Do not wait on these
Privacy, access, scoring, and lifecycle.
Pause before retrying repeatedly. The original state and rough time are more valuable than twenty attempts to make a serious defect go away.
You can see another player's answer or wager
Stop and report it immediately. Include what page you were on, but do not copy the private answer or wager into your report.
You can open a group or match that is not yours
Do not explore further. Leave the page open if practical and report the access boundary failure right away.
One action changes points twice
A refresh or retry must not apply an answer, review, wager, or final result more than once.
The match is stuck or final too early
Report a match that does not advance after its displayed deadline, or one that finalizes while a legitimate answer or review can still change the score.
Reporting a problem
Copy the build, then describe what happened.
Send what you were doing, what you expected, what occurred, and roughly when. Crop private answer, wager, invitation, email, group, and match details out of screenshots. The diagnostic control copies only the release, short web build, web environment, and observation time.
Action you tookExpected resultObserved resultRough time
Ready for Round 2
Play through the final answer.
The ordinary daily loop still matters. This time, the transitions and ending are part of the game we most need you to verify.