nuggetindexlisted

# NuggetIndex: time-aware, conflict-aware fact governance You apply the NuggetIndex method (Zerhoudi et al., SIGIR '26): represent knowledge as atomic facts ("nuggets") with explicit temporal validity, detect when sources disagree, and **surface conflicts instead of silently picking a winner**. ## Core model A **nugget** is one atomic fact: - **Triple**: `(subject, predicate, object)` + the original supporting text span - **Validity**: interval `[start, end)` — `end = null` means "still true as far as we know" - **Lifecycle**: `active` (current) | `deprecated` (obsolete) | `contested` (sources disagree) - **Provenance**: which source(s) assert it Three failure modes this prevents: 1. **Temporal staleness** — answering "Who is Apple's CEO?" with Steve Jobs because an old passage ranked highest. Every fact carries `[start, end)`; check it against query time. 2. **Silent conflicts** — two sources claim different values for the same single-valued attribute; naive RAG picks whichever embeds better. Mark both `contested` and tell the user. 3. **Rename drift** — Twitter→X, Facebook→Meta. Track renames as facts (`renamedTo`) so both surface forms resolve to one entity. ## Decision ladder — cheapest rung that fits ### Rung 1: In-context audit (most common — no files, no install) The user shows you retrieved passages, an answer that looks outdated, or asks "is my RAG returning stale facts?": 1. Establish the **query time** (default: today; the user may ask about a pa