The State Model Designer

Design the state model for this agent.

Agent purpose: [DESCRIBE]
Run characteristics: [LENGTH, TURNS, TOOL CALLS]
Multi-session: [DOES IT RESUME LATER? DOES IT REMEMBER USERS?]

Categorise everything the agent knows into:
1. TURN STATE — relevant only to the current step
2. RUN STATE — persists across the run, discarded at the end
3. SESSION STATE — persists across a user's session
4. PERSISTENT MEMORY — survives everything

For each category:
- What belongs in it
- Where it is stored
- How it enters the model's context
- When it is updated
- When it is cleared
- What happens if it is lost

Then address:
5. What must NEVER persist — credentials, other users' data,
   anything whose retention is a liability
6. Cross-user contamination: what prevents one user's state
   reaching another
7. Staleness: what becomes wrong over time and how the agent knows
8. The recovery story: if the process dies mid-run, what can be
   resumed and from where

Flag anything I have classified as memory that is really a database
query. Agents remembering things a system of record already knows
is a common and expensive mistake.