Latch

A small set of primitives that show up in every agent project we ship: a queue that survives restarts, a tool layer that handles auth and rate limits, a trace store that lets us replay any decision, and a skill system that lets one codebase fan out to many tenants.

We kept rewriting the same five things on every engagement. The fifth time was the one too many. Building it as a product — internally, before opening it up — is also the only way we trust it: every line gets put into client work before anyone calls it stable.

Internal. Pieces ship into client codebases as we harden them. A public release is on the timeline, not the calendar.