Prasith Govin

Founder, CTO, agent builder

I build small teams of AI agents that ship real software.

Prasith Govin photoshopped as Steve Jobs, in a black turtleneck holding an iPhone in front of the Apple logo at a keynote.

CTO and founder. Years running enterprise engineering, now building lean teams where a few people plus a fleet of agents do the work of a much larger org.

Tampa, FL GitHub X LinkedIn

01Building
4 active
  1. A voice-first assistant for people with effortful speech (built for my dad, who has Parkinson's). Reminders, medication timing, calls for help. Real-audio evals: 58% baseline comprehension → 82% with repair. 656 tests.

  2. My agent-orchestration stack, open-sourced: memory architecture, meta-learning loops, playbooks that let one operator direct many agents. v0.5.0, 8 production skills.

  3. Metadata-only receipts and fail-closed tripwires for agent trajectories. No content capture, zero deps, CI-gated.

  4. Shift marketplace and orchestration for the frontline workforce: matching, credentialing, scheduling, pay. Built with UKG Labs as partner and investor.

02How I build
  1. planPlan before code. The design doc comes first. If I can't write it down, it isn't ready to build.
  2. buildAgents build, I direct. Coding agents write the code. I set the spec, review the diff, and own the decision.
  3. reviewCross-model review by default. Every change is critiqued by a different model family before it ships.
  4. measureMeasured numbers only. Evals run with negative controls. I report what's measured, never what I'm hoping for.
  5. guardFailures become guardrails. Each failure turns into an executable check, not an apology.
  6. queueA night queue. Agents build while I sleep. Morning is for review.
04Notes
10 entries
  1. Jul 2026 my own repo disproved my readme I caught my own README overclaiming Parker, and the real eval number was better than the lie.
  2. Jul 2026 a repo can commit daily and still rot My agent audited our open-source sync and found three months of drift behind green CI and a daily commit streak.
  3. Jul 2026 guardrails, not prompts A prompt tweak fixes one bad output; a guardrail in the loop stops every one that fails the same way.
  4. Jul 2026 managing coding agents is managing juniors who forget everything overnight Coding agents are capable juniors with no overnight memory, so the work is in the brief, not the model.
  5. Jul 2026 a subagent dies quietly: the context-death contract Five subagents died in two weeks, all context blowouts, so the anti-death rules became a required contract on every spawn.
  6. Jul 2026 metadata-only receipts: trace, then tripwire Every agent run leaves a metadata-only trace that a fail-closed tripwire gates on before the next run proceeds.
  7. Jun 2026 the night build queue I set the plan at 10:30pm and agents build while I sleep; it only works if every run re-derives its numbers by morning.
  8. Jun 2026 two agents reviewing each other over a private channel Two agents on two machines reviewing each other produced our most novel work, and a six-hour deadlock that taught the most.
  9. May 2026 cross-model review is the default Every change gets reviewed by a different model family before it ships: one writes, one reviews, single round.
  10. May 2026 memory is the product surface For an agent, memory isn't a bolt-on feature; it gets a measured architecture with benchmarked recall and negative controls.