Memory architectures for AI agents.
Short, long, episodic, semantic — what each layer is actually for, and how the good agent systems wire them together.
I lead engineering at Metalab. Right now: AI-native client work, secure AI enablement, and the workflows that accelerate how engineers ship.
Each one shipped. Some are still in production; some were closed-source and are summarised. The full list is longer than is interesting to read.
“Curt is the best problem-solver I have ever worked with. We could get the outline of a business problem, sit on a meeting for two hours, and he'd have the technical requirements, scope, architecture diagrams, an ERD, and a low-fidelity design by the next day.”
Short transmissions on the systems behind AI delivery — memory, retrieval, agent loops, the un-fun parts. Cross-posted from LinkedIn.
Short, long, episodic, semantic — what each layer is actually for, and how the good agent systems wire them together.
Talking-head explainers ship semi-frequently — typically the week after I post them to LinkedIn. Subscribe there to catch the next drop.
Mostly on AI-native delivery, judgment as a priced layer, and what changes when execution gets cheap.
Software is a craft. These are mine. None of them are dogma.
A /now page in the Derek-Sivers tradition. Updated when it stops being true.
I lead engineering at Metalab — building AI-native client solutions, secure AI enablement for engineering teams, and the workflows that accelerate how engineers ship.
Last updated · 2026 · 04 · 12 — Open to staff & principal-level conversations
Open to staff & principal-level conversations. I read every note; expect a reply within a day or two.