Local useful loop
Optimize speed, portability, and one complete browser interaction.
- Gives up durable records and multiplayer
- Human steers; deterministic code automates calculation
- Static deployment, no service dependency
Simp / prototype decision surface
Three paths. One honest comparison.
Choose the smallest architecture that earns the interaction you need. These are proposed strategies grounded in the fused research; this page is the only implemented artifact in this showcase.
Planned ≠ real. A, B, and C below are plans. The real behavior here is selection and comparison only: no generated app, account store, database, realtime match, or runtime AI is connected.
The three planned strategies
Durable records
Optimize return visits with explicit authorization, saves, and recovery.
- Gives up live rooms and broad social scope
- Human confirms intent; server validates writes
- Persistent store, identity, backup evidence required
Authoritative play
Optimize trusted shared play and reconnect correctness.
- Gives up S1 simplicity and S2 breadth
- Clients send intentions; authority decides outcomes
- Realtime server, match rules, persistence boundary
Selected path: A — local useful loop
Evidence burden: replay the loop on target devices, then check keyboard, touch, errors, reset, and portability. Source grounding: the A plan and the S1 scope.
REAL in this showcase
Buttons update this comparison locally. Navigation and source links are real. No claim is made about the three proposed applications.