Five Across
Multiplayer bingo I built in eight days for a cruise and ran ten days at sea. The standings held, but the social mechanics barely caught on. A second event showed reusing the engine wasn't enough.
Every one of these began as a real problem—mine, or one I watched up close. The decisions are the part worth reading: what got built, what got refused, and what the evidence said once it was running. Each card says where the project stands, and why. I build with AI agents under a review system I designed and documented here. The agents are leverage; the product decisions are the point.
Multiplayer bingo I built in eight days for a cruise and ran ten days at sea. The standings held, but the social mechanics barely caught on. A second event showed reusing the engine wasn't enough.
A code-review standard for AI coding agents. Written rules didn't stop them pushing to main, so I built gates that could refuse. An audit then found eight of ten repos requiring none of five checks.
A Broadway deal model I built from my own investment documents, to learn the domain and test AI coding tools. It connects terms to investor outcomes but still hasn't run a real capitalization.
A device registry I built at Disney: five feeds, one schema. AI drafted the heaviest intake; every commit still needed an admin. The demo shows the workflow on invented data.
A career CRM that stops claims I can't trace to approved evidence. Paused before launch at 48% extraction and 19% match against an 80% bar I set before I'd built the ruler to read it with.
A swipe prototype that asks for taste before a viewer presses play. I let the demo promise better recommendations it didn't produce, so I couldn't separate reactions to the idea from the payoff.
Shared billing for nine people, with no recipient accounts. It took over the explaining and checking, but I kept getting the model right and stopping before the screen someone needed.