See the Work

Useful things shipped. A stack of undeniable proof.

A public record of building in public: learning what AI can do, using it in real time as an entrepreneur and dad, and sharing the lessons with the world.

Read the proof wall Use a tool

Build notes June 3, 2026

Every build here is judged by the problem it solves, the surface that shipped, and the proof signal it leaves behind.

20: tracked builds
10: ways to scan
5: first stops

Best First Proof

Start with the builds that explain the range.

Five first stops: a local utility, a serious dashboard, a photo product, a quiet family shelf, and a native app worth downloading.

Live macOS utility

Vellum

Problem: copy-paste heavy days make people lose useful context over and over.

Proof: a native-feeling utility with a clear privacy stance and a real everyday job.

Download ->

Live Field PWA

Savannah Shitlist

Problem: downtown restroom info is hardest to find at the exact moment people need it.

Proof: ranked local data, GPS UX, filters, and public-first usefulness.

Open site ->

Hosted demo Fleet intelligence

VoyagerAI Carnival

Problem: route, weather, and fuel risk need to be visible before ops decisions.

Proof: marine weather, fleet motion, and route-risk framing in a hosted dashboard.

Open demo ->

Live Photo product

EZ Photo Slideshow

Problem: event photos need a clean same-day playback surface without production drag.

Proof: upload flow, viewing surface, and delivery language built around real clients.

Open app ->

Private utility Family shelf

Cedar Story Shelf

Problem: book ideas, read-aloud notes, and shelf choices scatter across family life.

Proof: a practical reading room for recommendations, decisions, and follow-through.

Open shelf ->

Proof Index

Scan by problem, proof, and next step.

This is the evidence layer, not the runnable directory. Use it to see what each build was asked to solve, what it proves, and whether to run it, read it, play it, or ask about it.

Search builds

Showing all builds.

LiveAI diagnostic

When the proof maps to your work

Bring the constraint, not a vague AI wish list.

If one of these builds looks like a problem inside your company, start with AI Strategy or send the messy workflow directly.

AI Strategy -> Send the constraint ->

Useful things shipped. A stack of undeniable proof.