| Layer | Holds | Mechanism |
|---|---|---|
| Static context | The mandate, policy, and process that never change per query | Injected into every system prompt |
| Research library | Company profiles, sector analyses, source documents | RAG over a vector database |
| Prior work | Past decisions and memos | File navigation tools |
Layer 1: static context in the prompt
Rules that apply to every question belong in the prompt, not in retrieval. Load them once and inject them into every agent.Layer 2: the research library in RAG
The corpus the agents reason over goes in a shared knowledge base, searched per query. Instantiate it once and import it everywhere, never recreate it per agent.search_knowledge=True lets the agent pull the relevant profiles and analyses per question instead of carrying the whole library in context.
Layer 3: prior work on disk
Past memos and decisions are durable artifacts, not vectors. Give a read agent file tools so it can navigate the archive and ground new work in what was already concluded. The agent that writes new memos gets write access; the agent that reads them does not. Keep the boundary explicit.Why three layers, not one
| If you only had | You would lose |
|---|---|
| The prompt | A corpus too large to inline |
| RAG | Hard rules that must apply to every query, verbatim |
| The archive | The reasoning trail behind past decisions |
Next steps
| Task | Guide |
|---|---|
| Make grounded research compound | Institutional learning |
| End in an auditable artifact | Structured deliverable |