Simulation & Interactive Systems

Why I kept Sunday Lab and NBA Lab private, unified their forecasting vocabulary, and published the boundary instead of pretending two local prototypes were live products.

Reader outcome: Reader can separate facts, market observations, forecasts, decisions, and evaluations in a practice system without mistaking a private prototype for a live product or measured outcome.

The archive retrospective made the Games & Sim gap visible: three public proof pieces in a 96-post archive. The fix is not a better tagline; it is an artifact-first devlog cadence.

Reader outcome: Reader can audit a public pillar claim against archive evidence, then choose a proof cadence or retire the claim.

Why plausible synthetic customer behavior can turn an onboarding simulation into false evidence unless every journey claim has a trace and a real-world validation gate.

Reader outcome: Reader can design an agent-driven CX simulation as a hypothesis generator, with validation gates that keep synthetic behavior from being mistaken for customer evidence.

How Abuela's Unity gameplay loop and supporting web surfaces can share progression state, event contracts, reward rules, and iteration hooks without duplicating game logic.

Reader outcome: Promoted Abuela from a note to an essay by defining a loop architecture that keeps Unity runtime state, web companion flows, reward rules, and content iteration aligned.

A game economy design essay for Hippi Kingdom covering currency loops, sinks and sources, telemetry, a rejected progression model, and the balancing mistake that made hoarding look like engagement.

Reader outcome: Created an economy balancing framework that separates progression health from currency hoarding, making pacing, reward pressure, and retention tradeoffs easier to test.