What 461 Tickets Taught Me About Building AI Tools That Actually Work

I have spent the last 10 sprints building an AI-powered marketing platform. 461 tickets. 144 TypeScript services. 4,418 passing tests. Four blog posts in the retrospective series documenting every failure along the way. Here is what I actually learned. Not the technical details — those are in the series. The things that changed how I think about building AI systems. The tool description is the real API We built a memory system. Agents stored 64 memories. When we asked them to recall anything, they got zero results. Nine AI personas independently confirmed: the memory system is broken. It was not broken. The search used AND-matching on keywords. Agents wrote queries like humans write sentences: seven words long. The search needed two. The data was there the entire time. The fix was two lines of documentation in the tool description explaining how to format queries. Every hour we spent investigating the architecture, redesigning the storage layer, and filing risk assessments was wasted.