Evidence-driven product engineering
- Role
- Product Engineer · Full-Stack
Playable product · deterministic system
The architecture got better
every time the evidence disagreed.
One state powers UI, replay, restricted bots, simulation, and authoritative rooms. Evidence decides what ships.
- Rules truth
- Bot strength
- Network trust
- Resilience
- Performance + QA
Real product evidence

Swipe through the evidence01 / 05
- Shared system core
The interface could guide legality.
GameState + ActionPure reducerOne deterministic output powers every surface.
- State + action log
- React + replay
- Restricted bots
- Simulation
- Online rooms
- Evidence-led correction
A single Elo-like number was enough.
01Mirrored deals02Seat swaps03Glicko-204Focused gates05Human dogfoodRatings guide experiments. They do not become product truth automatically.
- Evidence-led correction
Face-down placeholders hid private state.
one projection boundaryPlayer Aown hand + public evidencePlayer Bown hand + public evidenceBotViewown hand + public evidenceOpponent hands, undealt order, and reconstructive seeds stop here.
- Evidence-led correction
A closed socket meant the player left.
Socket closesNetwork transitionSeat remains ownedPrivate view preservedClient reconnectsSame turn · same room - Evidence-led correction
The release surface was already small and touch-safe.
Bundle · minified≈506 KB≈399 KBTouch controls30 / 40 px44 pxSix themes × mobile, tablet, desktop.