Memory and limits

Use run state for work that belongs to a single execution. Use durable memory for facts that should survive a run and remain scoped to the agent, entity, and workspace that own them. Store meaningful artifacts and decisions rather than an unbounded conversation transcript.

Every run should have ceilings for time, concurrency, and spend, plus a clear policy for tool access. When a ceiling is reached, stop the run with a reason that an operator can investigate. Limits are controls, not performance targets.