Can different clues become a memorable social competition?
Keep teams synchronized, hints timed, and progress shared without exposing answers to the client.
CASE FILE. 06 / PUZZLE / SOCIAL GAME
Desafio Online
A platform for pairs and groups with teams, invitations, and persistent expeditions. The Impossible Map combines clues, timed hints, and shared progress.
- Next.js 16
- React 19
- PostgreSQL
- Drizzle
- Firebase Auth
BRIEF. 01 / PROBLEM AND BOUNDARY
The product in one read.
A deliberate view of the current state. Metrics and the hypothesis remain editorial until public evidence can replace them.
- FORMAT
- PAIRS + GROUPS EDITORIAL LABEL
- EXPEDITION
- IMPOSSIBLE MAP EDITORIAL LABEL
- CAPABILITIES
- 4 frontend / backend / data / integrations
- PUBLIC DOOR
- YES VALIDATED DEPLOYMENT
SYSTEM TRACE. 02 / PRIMARY FLOW
Boundaries before frameworks.
Expedition interface → server-side team actions → persistent PostgreSQL progress → Firebase identity.
- 01EXPEDITION→
Team interface
Next.js / map and clues
- 02COMMAND→
Server actions
Submission, hint, and readiness
- 03PROGRESS→
Game state
PostgreSQL + Drizzle
- 04IDENTITY
Access boundary
Firebase Auth / invitations
intent → policy → authoritative state → observable effectEXECUTION TRACE / ILLUSTRATIVE
One path. Every decision in view.
An editorial sequence for discussing contract, authority, and effect. It does not represent real production telemetry.
- IDENTITY
Confirms identity, invitation, and expedition membership.
member.authorized - COMMAND
Normalizes the attempt without returning the expected solution.
answer.checked - PROGRESS
Records the attempt or advancement in an idempotent transaction.
progress.version + 1 - EXPEDITION
Projects clue, timer, and shared state to the team.
team.synchronized
DECISION LOG. 03 / TRADE-OFFS
Every choice costs something.
Keep solutions and progression authoritative on the server; the browser receives only the state required for the current stage.
- 01 / SECRET
Answers only on the server
- GAIN
- The client never receives the solution before clue validation.
- COST
- Preview and offline modes remain deliberately limited.
- 02 / TEAM
Authoritative shared progress
- GAIN
- Everyone sees the same expedition, hint, and completion order.
- COST
- Simultaneous actions need idempotency and explicit conflict handling.
- 03 / CONTENT
Clues as composable mechanisms
- GAIN
- An expedition combines logic, media, and interaction without one screen per game.
- COST
- The editorial schema must limit complexity and validate each type.
RELIABILITY. 04 / FAIL WITH CONTEXT
Failure mode. Signal back.
These are not published production metrics. They are risks the design must make observable and candidate signals for the next round.
- 01
Two people submit the correct solution at the same instant.
- 02
The hint clock diverges after suspension or a device change.
- 03
An answer or future clue appears in the browser payload.
- 01
Completion time and hint-use rate by clue mechanism.
- 02
Idempotent conflicts and recovery without progress regression.
- 03
Accepted invitations, ready teams, and expeditions actually started.
INCIDENT DRILL. 05 / CONTAINMENT → RECOVERY → PROOF
When the hypothesis breaks.
Editorial resilience exercises, not real incidents or production runbooks. Each drill turns a failure mode into a response that can be discussed and tested.
DRILL-01Two people submit the correct solution at the same instant.SIMULATION / NATIVE
Response to: Two people submit the correct solution at the same instant.
- CONTAIN
- Compare and update the expedition version inside one transaction, accepting a single advancement.
- RECOVER
- Respond to the second command with the already-advanced state, without treating it as a new completion or penalty.
- PROVE
- Demonstrate one advancement event, one next position, and an invariant ranking under concurrent repetition.
DRILL-02The hint clock diverges after suspension or a device change.SIMULATION / NATIVE
Response to: The hint clock diverges after suspension or a device change.
- CONTAIN
- Ignore client clocks and calculate eligibility only from the server-persisted deadline.
- RECOVER
- Resend reference instant, deadline, and current state when the team resumes the expedition.
- PROVE
- Simulate different local clocks and confirm the same hint release for the whole team.
DRILL-03An answer or future clue appears in the browser payload.SIMULATION / NATIVE
Response to: An answer or future clue appears in the browser payload.
- CONTAIN
- Block the affected route and immediately remove the secret field from the client contract.
- RECOVER
- Move validation and resolution to the server, invalidate caches, and build a new artifact without the solution.
- PROVE
- Inspect HTML, RSC, JavaScript, and network to confirm future content never crosses the public boundary.
DESIGN EXERCISE / REVIEW AGAINST REAL TELEMETRY AND RUNBOOKS BEFORE OPERATING
EVIDENCE. 06 / WHAT CAN BE DEFENDED
Facts in view. Gaps too.
Instrument clue difficulty and completion rankings, then build editorial tools for new expeditions.
- Next.js 16 + React 19
- PostgreSQL + Drizzle
- Firebase Authentication
- Hackathons + treasure hunts
INTERVIEW MODE. 07 / DEEPEN THE CONVERSATION
Three points to open on the board.
Questions that connect the case to system design, product, and operations without turning a contextual decision into a universal rule.
- 01
How to create new clue types without spreading conditionals across the product.
↗ - 02
How to define a fair ranking when network and team actions vary.
↗ - 03
How to test secret content without letting it reach the client bundle.
↗
CASE FILE / 06