Udi Levy

This is how I think, and how I build with AI.The light is a thought. The threads are what pulls on it. You steer.

Yehuda (Udi) Levy · Principal Architect and Developer

Start from the outcome, establish what's true, keep control of anything irreversible, shape it for the experience, and make the knowledge outlive the session.

1. Outcome: TuckABook

pages drawn one at a time drift. Faces swap, characters blend, and words painted into the art come out misspelled.

what has to be true for a family. Their people, on every page.

cast first. Each person becomes a locked sheet, every page is drawn from the sheets, a second model checks for drift, and the words are lettered on top.

2. Truth gate: the airline database

timeouts kept coming after the database was scaled up. The loud answer was "database saturation".

how do we know? The database query itself was fast. Small serverless CPU allocations were starving the TLS handshake.

A/B proof, then a permanent fix in infrastructure code with a written rollback plan. The handshake dropped from seconds to a fraction of a second. Repeatedly across investigations this year, the key move was correcting a louder conclusion.

3. Control gate: gate

adversarial review found working exploits in the first version, most of them the agent finding a way to become its own approver.

can this be undone, and who said yes?

the tool decides and the agent classifies, by exit code. Doubt fails closed. Most checks in the first month came back Ask, on purpose.

4. Shape: the me app

the agent talked too much, in the wrong place, and the pacing rules lived in prose that drifted.

way too many words. One thing at a time.

one ranked queue, one card at a time with a preview, one tap to answer. The pacer holds back low-priority pushes until a quiet window.

5. Persist: corrections become rules, and the toolkit

narration leaked into chat, and a tap on the agent's own card once looked like his yes.

a promise to do better isn't a fix.

each correction becomes a dated rule in the file agents read every turn. At work, the same idea became a read-only AI toolkit that peers across teams adopted.

  • TuckABook
  • a locked character sheet
  • a slow handshake made fast
  • from contractor to principal
  • the year I taught myself to code
  • one tap, with a preview
  • one door per risk
  • "how do we know?"
  • sub-agents in parallel
  • Sunday table
  • bedtime stories
  • "Adventure's Out There"

Udi Levy

I'm Udi, and I live in Pearland, Texas. By day I'm a Principal Architect and Developer at United Airlines. At night I build AI agents, and TuckABook, where families make storybooks about their own people.

Our family motto is "Adventure's Out There." Go find out, then bring back what you learned.