AP.
ask me anything
>
try:

I buildwhat deckspromise.

Backend systems and AI agents. Ship before polish.

shipped Atlas Runtime v111M events/day on HalfpipeSieve replaced a $4k/mo vendorshipctl: branch → live in 47sBoring AI: 14k readsopen to founding eng rolesshipped Atlas Runtime v111M events/day on HalfpipeSieve replaced a $4k/mo vendorshipctl: branch → live in 47sBoring AI: 14k readsopen to founding eng roles
scroll for proof
03 / operating system

What I reach
for, why, and
when not to.

Tools are arguments. These are the ones I'm willing to defend in a code review at 11pm. Substitutes welcome — the ratio of opinion to dogma matters more than the brand on the lid.

01

Build

What I reach for first.

TypeScriptGoPythonPostgres
02

Reason

Where the AI work lives.

GPT-OSSAnthropicpgvectorModal
03

Ship

How it gets to a user this week.

VercelFly.ioLinearCursor
04 / receipts

The log,
not the resume.

Years employed is a useless metric. Things shipped is the metric. Recent first.

  1. 2025

    Shipped Content Repurposing Engine. AI-powered content transformation platform.

  2. 2025

    Built Health Label. Instant science-backed health ratings from barcode scans.

  3. 2026

    Created Alpha Audit. Autonomous corporate integrity auditor with SEC cross-referencing.

  4. now

    Looking for the next thing to break in production for the right reason.

05 / thesis
why I'm available

Most AI work in 2026 is still a demo dressed as a product. The interesting work is the part nobody posts about: the retry logic, the idempotency, the cache that survives a bad deploy. I want to be the engineer you call when the wrapper breaks and there's nothing on Stack Overflow yet.

signed, the engineer
06 / handshake

Tell me what
you're building.

One line. What you're building. I reply in a day.

built by hand · 2026/India