Skip to main content
Paper·arxiv.org
ai-agentsragcontext-engineeringinfrastructureresearch

Retrieval Is Not Enough: Why Organizational AI Needs Epistemic Infrastructure

Augment AI retrieval (like RAG) for organizational knowledge by adding 'epistemic infrastructure.' This involves categorizing information by its validity and status, ensuring AI agents differentiate between facts, decisions, and hypotheses for reliable outcomes.

intermediate1-2 hours5 steps
The play
  1. Identify Critical Information Types
    Analyze your organization's knowledge base. List distinct categories of information that AI agents interact with, such as 'binding decisions,' 'project proposals,' 'research findings,' 'meeting minutes,' 'abandoned hypotheses,' or 'settled facts'.
  2. Define Epistemic Statuses
    For each identified information type, define a set of 'epistemic statuses' that describe its validity, currency, or intent. Examples include 'final,' 'draft,' 'approved,' 'deprecated,' 'speculative,' 'confirmed,' 'superseded,' or 'active'.
  3. Design an Epistemic Tagging Schema
    Create a structured schema (e.g., JSON, YAML) to represent these information types and their corresponding epistemic statuses. This schema will be used to tag your organizational data. Consider hierarchical structures if statuses can be nested.
  4. Integrate Tagging into Knowledge Ingestion
    Implement a process to apply these epistemic tags to your documents and data as they are ingested into your knowledge management system or AI retrieval pipeline. This might involve manual tagging, automated classification, or metadata enrichment.
  5. Leverage Epistemic Tags in AI Agents
    Modify your AI agent's retrieval and reasoning logic to filter or prioritize information based on its epistemic status. For example, instruct the agent to only consider 'final' and 'approved' decisions when answering policy questions, or to flag 'speculative' content.
Starter code
```json
{
  "document_id": "ORG-DOC-001",
  "title": "Q3 2024 Product Strategy Meeting Minutes",
  "content_summary": "Discussion on new feature roadmap and market analysis. Key decisions made on feature prioritization.",
  "epistemic_metadata": {
    "information_type": "meeting_minutes",
    "status": "final",
    "validity": "binding_decisions_included",
    "date_reviewed": "2024-09-30",
    "source": "executive_board"
  }
}
```
Source
Retrieval Is Not Enough: Why Organizational AI Needs Epistemic Infrastructure — Action Pack