Agent treats all documents with equal temporal weight. Cannot distinguish between current policy and superseded version. Cannot detect that a document has been revised.
When an agent retrieves documents (policies, procedures, guidelines, forms) to inform its reasoning, it often cannot distinguish between the current version and a superseded version. If both versions are accessible in the agent's knowledge base or document store, the agent might reason from either one without awareness that one is obsolete.
This is particularly problematic when an organization revises a policy but does not delete the old version (which is common in document management for audit trail purposes). The agent might retrieve the old version, reason from it, and make decisions based on policies that are no longer in effect.
This is fundamentally agentic because agents are designed to retrieve and reason from documents autonomously. A human, by contrast, would naturally recognize an outdated document by its revision date or format and would discard it in favor of the current version.
A bank's lending agent is designed to make credit decisions according to the bank's credit policy. The agent retrieves the credit policy document from the document management system to inform its decision logic. The policy is a complex document with many pages of rules and thresholds.
Six months ago, the bank updated its credit policy in response to a change in the regulatory environment. The new policy was issued on January 1 and is the current policy. The old policy document is still in the document management system (because the bank keeps old policies for audit trail purposes), but it has been superseded.
The agent, when retrieving the credit policy, has access to both versions. The agent retrieves the first document it finds, which happens to be the old policy. The agent reasons through a credit decision using the old policy: "Loan applicant must have minimum credit score of 650; applicant's score is 680, so APPROVE."
However, the current policy (which was updated on January 1) specifies: "Loan applicant must have minimum credit score of 700; applicant's score of 680 does not meet current requirements; DENY."
The agent approves a loan under the old policy that would be denied under the current policy. The loan is issued. Three months later, the applicant defaults. During the post-default investigation, the bank discovers that the decision was made using an obsolete policy.
| Dimension | Score | Rationale |
|---|---|---|
| D - Detectability | 4 | Version blindness is invisible unless document version numbers are explicitly checked. |
| A - Autonomy Sensitivity | 4 | Agent retrieves and reasons from documents autonomously without version awareness. |
| M - Multiplicative Potential | 3 | Impact depends on how many decisions are made from obsolete documents and how different they are from current policy. |
| A - Attack Surface | 5 | Any agent that retrieves documents without version control is vulnerable. |
| G - Governance Gap | 5 | No standard framework requires agents to validate document version currency. |
| E - Enterprise Impact | 3 | Decision errors, policy violations, potential credit losses, regulatory finding on document controls. |
| Composite DAMAGE Score | 3.3 | High. Requires targeted controls and monitoring. Should not be accepted without mitigation. |
How severity changes across the agent architecture spectrum.
| Agent Type | Impact | How This Risk Manifests |
|---|---|---|
| Digital Assistant | Low | Human reviews documents and naturally selects current version. |
| Digital Apprentice | Medium | Apprentice governance requires use of version-controlled documents. |
| Autonomous Agent | High | Agent cannot distinguish between current and obsolete document versions. |
| Delegating Agent | High | Agent invokes tools based on obsolete policy documents. |
| Agent Crew / Pipeline | Critical | Multiple agents in sequence use obsolete documents. |
| Agent Mesh / Swarm | Critical | Agents share obsolete documents. |
| Framework | Coverage | Citation | What It Addresses | What It Misses |
|---|---|---|---|---|
| SR 11-7 / MRM | Addressed | Document Management and Controls (Section 2) | Expects organizations to maintain current policy documents and control versions. | Does not address agent use of policy documents. |
| NIST CSF 2.0 | Partial | GV.RK-1 | Recommends maintaining accurate information about organizational policies. | Does not address agent policy document use. |
Policies are foundational to regulated operations. Banks, insurers, and healthcare providers must ensure that all decisions are made in accordance with current policies. If an agent makes decisions based on obsolete policies, those decisions are outside the approved operating framework.
Under SR 11-7, regulators expect that policies are clearly versioned and that all decision-making systems (including agents) use current policies.
Document Version Blindness requires version-controlled policy systems purpose-built for agent consumption. Our advisory engagements are designed for banks, insurers, and financial institutions subject to prudential oversight.
Schedule a Briefing