SCOI Atlas · L6 Orchestration
L6D Context & State Management
What the agent knows at any moment: session, thread, run, task, world.
TL;DR · Direct answer
L6D Context & State Management is a sublayer of L6 Orchestration in the Supply Chain of Intelligence™ (SCOI) by Anand Arivukkarasu. It is a required capability but not on its own a durable moat. Treat context as a database. Design its schema before you design the agent loop.
What actually matters at L6D
- Context windows are still finite, and cost scales quadratically at some providers.
- State schemas outlast models; design them like a database, not a prompt.
- Context leakage across tenants is the #1 enterprise incident category.
The startup lens
Treat context as a database. Design its schema before you design the agent loop.
Vertical lens — how this plays across categories
Enterprise AI
Per-tenant, per-user, per-run state boundaries enforced in code.
Support AI
Ticket + customer + product state as first-class objects.
Consumer AI
Explicit user-owned memory with delete/export.
How to defend L6D
- State schema in a real store, not the prompt.
- Tenant isolation reviewed as a security control.
Other sublayers in L6 Orchestration
L6A
Agent Loops
Plan-execute-reflect loops; ReAct; multi-agent choreographies.
L6B ★
Human-in-the-Loop
Where and how humans check, correct, or approve agent work — and how those signals train the system.
L6C
Role Routing & Task Decomposition
Breaking work into subtasks and routing each to the right skill, tool or sub-agent.
L6E
Runtime Assurance & Learning Loops
Live monitoring, drift detection and the loops that improve the system from production data.