Skip to main content

14 posts tagged with "AI in Production"

Closing the gap between an AI demo and a system you can run.

View All Tags

From Vibe Coding to Spec-Driven Development to Loop Engineering

· 9 min read
CatalEx Engineering
The team building CatalEx
CatalEx Engineering · Published July 3, 2026 · 09:00 UTC

Every team that builds seriously with AI walks the same road, usually without noticing. It starts with a chat window and a good feeling, and — if the work survives contact with production — it ends somewhere far more disciplined. This is a field note on that road: the three stages we see teams pass through, what each one is genuinely good at, and the specific failure that forces the jump to the next.

Memory That Compounds: What "Persistent" Actually Means for an Agent

· 6 min read
CatalEx Engineering
The team building CatalEx
CatalEx Engineering · Published July 2, 2026 · 09:00 UTC

"Give the agent memory" is one of those phrases that sounds like a feature and is actually an architecture. Everyone agrees agents should remember things across sessions. Almost no one agrees on what that means — and the default implementation, a vector database that everything gets dumped into, produces agents that are confidently wrong about their own past.

The Harness Is Half the Model: Why Scaffolding Decides Performance

· 7 min read
CatalEx Engineering
The team building CatalEx
CatalEx Engineering · Published June 30, 2026 · 09:00 UTC

The most expensive misconception in applied AI is that performance lives in the model. Pick the best model, the thinking goes, and the rest is glue. So teams spend their attention on which model to call and treat everything around it — the tools, the loop, the context they assemble, the way they check the output — as plumbing.

How We Keep Claude's Context Lean While Building CatalEx

· 6 min read
CatalEx Engineering
The team building CatalEx
CatalEx Engineering · Published June 27, 2026 · 09:00 UTC

When you build software with an AI agent day to day, the thing you run out of first isn't intelligence — it's context. The window is finite, attention inside it isn't free, and a session that starts sharp gets duller as it fills with the exhaust of the work: verbose command output, whole files read to find one function, stale documentation, the residue of three tasks ago.