On conflict, a verified memory outranks freshly retrieved context
A verified record beats a document an agent found mid-run, unless the document is newer and cites its source.
The record
Agents retrieving live documents kept re-deriving conclusions the enterprise had already settled, sometimes reversing them. Precedence is now explicit: a verified memory wins ties against retrieved context. A retrieved document overrides one only when it is both newer and sourced, and when it does, the agent must file the correction as a memory update rather than acting silently.
Applies to
- Company
- All companies
- Department
- All departments
- Agent
- No single agent
Facts true across every company. The operating doctrine. Readable by: Every agent, every company.
Provenance
Retrieval policy, 15 Jul 2026
Decision log · human in the loop
- Recorded by
- Ines Marchetti (CAO)
- First learned
- 15 Jul 2026
- Last updated
- 15 Jul 2026
Index state
Not embedded- Index
- enterprise-core
- Vector id
- —
- Model
- —
- Indexed at
- —
- Rank weight
- 1.20
No vector store is connected, so this record has no embedding. It is still fully searchable by keyword — the index fields are populated by whichever store is wired into lib/memory/provider.ts.