BUILDS
Small problems.
Open implementations.
These begin with a problem I actually had—or one I saw close enough to care about. The result is a working system, not only a description of one.
Every build opens into the outcome, architecture, source, instructions, trade-offs, and honest notes about what is not finished yet.
LATEST BUILD NOTE
Useful first. Reproducible by default.
01 / FRAUD + VOICE AI
Fraud-Fighting AI Granny
A voice agent designed to consume a scammer’s time without putting a real person—or real personal information—into the conversation.A public Node.js prototype that answers a Twilio call, listens, generates an in-character response, synthesizes speech, and keeps the exchange going within a bounded conversation.
THE BUILD PROTOCOL
A repeatable path from annoyance to public utility.
Future project chats can use this same record, so the page and repository evolve together.
- 01
Start with friction
A problem experienced directly, or observed close enough to understand the real constraint.
- 02
Ship the smallest system
Enough product to change the outcome—not a speculative feature inventory.
- 03
Open the implementation
Architecture, source, setup, trade-offs, failure modes, and what still needs work.
- 04
Leave a trail
A durable build note that another person—or agent—can inspect, reproduce, and extend.
EARLIER PUBLIC CODE
The trail started before the showcase.
These are source-linked artifacts, kept in their original context. They can become full build notes when revisited.
NEXT SLOT
Bring the problem. We will leave the solution open.
Problem → plan → working product → public repository → build note. The next project starts in a new chat and lands here when it earns its place.