Google ADK Tiered Context Architecture: Compile Working Context from Session + Memory + Artifacts Like a Compiler Optimizes Code — Cache-Friendliness as Hard Constraint

Google Developers Blog·medium signal

Google's Agent Development Kit treats context as a compiled system, not a string buffer. Three layers separate storage from presentation: Session (chronological interaction history), Memory (long-term cross-task knowledge), and Working Context (ephemeral optimized view). The Working Context is compiled each turn — like a compiler transforming source into machine code — by processor pipelines that compact history, retrieve relevant memory, and reference artifacts. Critically, ADK lets you order your pipeline to keep frequently reused segments stable at the front of the context window for cache hits, pushing dynamic content to the end.