Demo Lab
I use this lab to turn architecture, state machines, timing, and failure recovery into small interactive reconstructions. Instead of only describing what I built, I can let you run it, break it, and watch the system respond.
Available now
These demos are grounded in preserved project evidence: enough fidelity to show the engineering decisions while keeping proprietary systems generalized where necessary.
Demo 01
Interactive crypto kiosk controller
I reconstructed a production cash-recycler controller as an explorable kiosk. Follow a buy or sell transaction from the customer screen through escrow, authorization, stacking, payout, inventory updates, callbacks, and recovery — then inject failures to see how the controller protects physical reality.
Demo 02
All ten browser titles running through one modernized shared engine
Switch among all ten archived title packages and play them in a polished 1024×768 CreateJS runtime. The revival preserves the original wager ladder, weighted selection model, title-specific payline counts, payout scaling, and nine-plus-one architecture while modernizing animation, state, controls, and responsive scaling.
Demo 03
Change a production foundation without gambling with production
Reconstruct a live CRA/Heroku to Next.js/Vercel migration as a controllable release system. Map dependencies, prepare rollback, rehearse, validate health, move traffic, inject failures, and watch explicit go/no-go gates refuse unsafe changes — including Brenda mode.
Demo 04
Replace the spreadsheet as the workflow without losing the work inside it
Start with three spreadsheet copies that disagree. Find the source files, map and clean the fields, group duplicates, stop on conflicts, verify the fixes, and only then publish. Then switch to New dispute to see how the spreadsheet disappears from the workflow entirely. Brenda is there if you want to try publishing something that absolutely should not ship yet.
This is the beginning
I plan to use it for more interactive system stories where a static architecture diagram cannot quite capture timing, state, tradeoffs, or how a product behaves when something goes wrong.