Evidence
Shipped, not slideware including the parts that aren't finished.
Each of these leads with the constraint rather than the stack. Anyone can list technologies; the constraint is what tells you whether someone thinks about your problem the way you need them to.
Two of these are personal projects rather than client work, and they say so. Two further systems — multimodal extraction with end-to-end provenance, and document extraction with auditable confidence scoring — are client work and are not published.
Mine outright
ColdDeck
cold email that reads like you actually looked.
Prospect scoring where every point traces to the page that produced it, and a human approves every email before it sends. Demonstrates all four commitments at once.
A rule pack, not a model.
Stack
ColdDeck
deterministic prospect scoring · human-gated send
Approval queue — one email awaiting review
screenshot pending
Commissioned
Agent OS
a second brain the agent edits in the open.
State kept as markdown files rather than in a database, so what the agent changed is reviewable the way code is. The cost of that choice is written down too.
Every agent action is a git diff.
Stack
Agent OS
markdown-native agent runtime
Dashboard — vault rendered as deals and notes
screenshot pending
Mine outright
authority-wizard
eighty pages that agree with each other.
Django and Celery producing book-length output. The hard parts are coherence across chapters and not losing the work when chapter twelve fails.
Orchestration, not prompting.
Stack
authority-wizard
long-form generation platform
Generation in progress — chapters completing independently
screenshot pending
Personal project
agentic-ai
it asks first, every time.
Characters as folders of plain files — hand-editable, diffable — with agents that halt for approval before writing. Plus a deployment model most teams miss.
Agents that stop before they change anything.
Stack
agentic-ai
approval-gated agent runtime
Approval prompt — the agent describing an intended write
screenshot pending
Personal project
DripDeck
neither clock needs you awake.
Scheduled publishing where the machine never needs to be awake at the right moment, and days it was off self-heal on the next run.
The queue may fall behind. It may never silently stall.
Stack
DripDeck
self-healing publish scheduler
Queue view — slots filled, missed, and reassigned
screenshot pending
Also shipped
Not case studies — there is no single decision in these worth a page. Listed because range comes up on most first calls, and because the lineage matters: several of the ideas above were first attempted here.
in any of these? Let's talk about it.