Production engineering · AI agents · SRE

Production Notes

Build AI agents you can debug, evaluate, and operate.

Practical notes on runtimes, tool calls, incident investigations, and the unglamorous controls that make agent systems useful after the demo.

Featured by CNCF: You Can’t Debug What You Can’t See — Observability for AI Agents

Start with a production problem

No need to read the whole archive. Pick the problem in front of you and follow a focused path.

Choose a reading path

Path Best for
SRE on-call starter pack Triage, RCA, observability — 5 posts
SRE as service starter pack Investigation as a service product — 5 posts
Go agent runtime starter pack Runtime definition, Go vs Python, platform split — 5 posts
ClickHouse on AWS starter pack Self-managed ClickHouse from first principles — full series
Full enterprise AI agent series Searchable archive in full reading order
Service Rendered Efficiently AI investigation as a service product for on-call

Pocket checklists

Copy these into an incident review or agent launch review. No proprietary schemas required.

Browse by topic

About these notes

I’m Sabith K S, a Principal Engineer at StackGen. I write about the systems we build, the mistakes we make, and what we can learn from them. The examples often come from building Aiden, StackGen’s platform for running agents for multiple teams, and from site reliability engineering (SRE) work.

These are engineering notes from a particular production setting, not a claim that every team needs an agent—or needs to build one in Go.

Connect