3 Levels of Observability for Coding Agents

In this blogpost I am exploring how a framework that translates code into a graph fits within the observability stack. Intuitively, something that helps decompose a pipeline code into its corresponding elements should help - it should help coding agent with testing & verification, optimized debugging, auditability. It should help a host of coding agent architectures, especially with longer-term horizons. But this blogpost is trying to explore less of what it can do, and of where this framework fits in.