Context is constructed, not stored

The most important reframing: context is not a thing you keep; it's a thing you build fresh for every model call. Each call, your orchestrator assembles:

• the system prompt (identity, rules, output protocols),
• the relevant slice of conversation history,
• the available tools,
• and injected information (what's available to act on, retrieved snippets, prior-turn summaries).

The model is stateless between calls. "Memory" is your database; "context" is the carefully-chosen subset of that memory you load into a given call. The skill is in the choosing.