Agent memory should help interpret a task, while durable workflow state governs what may happen next. A generated recollection cannot reliably establish whether a booking committed, permission changed, or another worker already owns the action.
Memory and business state serve different roles
Agent memory contains conversational context or selected past information used during reasoning. Business workflow state records the current operation, permissions, confirmed intent, effects, and accountable owner under trusted application control.
For a proposed architecture, store operation identity, intent revision, stage, resource versions, and authoritative results in a durable service. Agents read the permitted current snapshot and submit bounded proposals. The execution boundary validates those proposals against current state.
Do not let an agent overwrite the state merely by asserting that an action succeeded. Completion needs evidence from the system responsible for the business effect. Keep narrative summaries as supplementary context.
Test a fictional restart and handoff
An intake agent confirms an address, then a worker creates the service request. The agent process restarts before receiving the result. Its replacement should inspect the durable operation and recover the authoritative reference rather than create the request again from remembered intent.
A second fixture gives the replacement agent an outdated summary. The current state contains a caller correction. The workflow must use the current revision and reject proposals based on the old address.
| Disagreement | Trusted decision source |
|---|---|
| Agent recalls a completed write | Authoritative operation result |
| Summary contains old date | Current confirmed intent revision |
| Two agents claim ownership | Workflow assignment authority |
| Permission changed | Current trusted policy |
| Resource edited by staff | Authoritative resource version |
Inspect final records and transitions under controlled concurrent attempts. A coherent final conversation does not prove that stale internal memory was prevented from causing a side effect.
Keep state minimal and inspectable
A durable state service need not store every message. Persist the facts and references required for safe execution, recovery, and review. Minimise personal content and apply role-based access to the task snapshot.
External state adds latency, schema maintenance, and coordination. For consequential workflows, those costs buy observable boundaries and recovery. For low-impact exploratory tasks, a lighter design may be sufficient, provided its limits are explicit.
This architecture is proposed. The voice platform case study describes relevant backend work without claiming this multi-agent state service. Pair it with database workflow state.
Agent memory FAQ
Can a summary be the source of booking truth?
No. Use the authoritative booking or operation result.
Must every message be persisted as state?
No. Keep the minimum business facts and evidence references needed for the workflow.
What should happen when memory and state disagree?
Apply the trusted current state and investigate or clarify the discrepancy before a consequential action.