BUILDS
The strongest work starts with a real problem and ends with something people can use or inspect.
Closed-source products show the product decisions, trust model, and measured outcome. Open-source builds add the implementation and a public repository.
PRODUCT SHOWCASE
01 / WEB + IOS + ANDROID + PRIVACY
One shared web, iOS, and Android product with a 603-source registry catalog, consented public-search discovery, an encrypted identity vault, guarded standing authorization, first-party request execution, protected government handoffs, and privacy-safe reports.
02 / IOS + IPADOS + MACOS
One universal Apple app that gives families useful offline pages, parent-controlled custom creation, direct printing, in-app coloring, school-art capture, local search, and keepsake books.
03 / MACOS + STORAGE INTELLIGENCE
A native Mac app that explains the largest causes, puts the safest useful review first, names what will stay untouched, and verifies the result.
OPEN-SOURCE SHOWCASE
Each project links to a readable build note and the repository that supports it.
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.
EARLIER EXPERIMENTS
These repositories are public code, not complete products. They stay visible without competing with the work above.
NEXT SLOT
A product can stay private, or its source can remain open. Either way, the record should make the problem, decisions, and working result clear.