Problem Statement
Truth-maintenance retrieval filtering can reject candidates whose declared facts or source supports are no longer active. A complementary assembly layer is needed to validate retrieved text, cached summaries, and structured citations against one immutable truth view.
For example, if source A is withdrawn while source B still supports the same conclusion, fact-only content may remain valid, but a summary citing A must not retain that withdrawn citation. Late corrections also require distinguishing what was valid at a given time from what was known at that time.
Proposed Solution
Add an opt-in context assembly layer that:
- Captures one immutable truth view from a regular session or a bitemporal adapter.
- Registers immutable summaries and citations with explicit fact and source-support dependencies, supporting dependency-based eligibility and stricter snapshot-bound eligibility.
- Reconciles registered content against new views, reporting invalidation and restoration.
- Validates ordinary annotated candidates and registered summaries before ranking and top-k selection.
- Renders complete context blocks and their citations deterministically within a character budget.
- Rejects assembly if the relevant truth-source or registry revision changes before return.
- Supports historical reads without changing live eligibility.
Acceptance Criteria
- Withdrawing the final support removes dependent content.
- Withdrawing one source preserves independently supported facts but excludes summaries citing the withdrawn source.
- Snapshot-bound summaries become ineligible after a snapshot change, including fact additions.
- Late corrections produce consistent results for independent valid-time and knowledge-time coordinates.
- Budgeting includes citation and formatting overhead; blocks are not truncated and orphan citations are not emitted.
- Historical reads do not mutate live state.
- Incremental eligibility matches an independent full-recomputation oracle.
- Existing retrieval behavior remains unchanged unless the new path is explicitly used.
Scope and Alternatives
This is limited to local retrieval and explicitly declared dependencies. It does not generate or rewrite summaries, infer dependencies, manage all community-summary caches, delete stored vectors, or extend global/DRIFT/hybrid retrieval.
Manual post-filtering and full cache eviction remain alternatives, but do not by themselves bind selected text, summaries, and citations to the same view.
The guarantee concerns declared dependencies at assembly return—not natural-language correctness, model-answer correctness, or transactional consistency of external stores. Calls must be serialized by the application.
Impact and Related Work
Additive API, no new runtime dependencies planned. Builds on #1544, #1556, and #1675.
I am willing to contribute the implementation, regression tests, and documentation.
Problem Statement
Truth-maintenance retrieval filtering can reject candidates whose declared facts or source supports are no longer active. A complementary assembly layer is needed to validate retrieved text, cached summaries, and structured citations against one immutable truth view.
For example, if source A is withdrawn while source B still supports the same conclusion, fact-only content may remain valid, but a summary citing A must not retain that withdrawn citation. Late corrections also require distinguishing what was valid at a given time from what was known at that time.
Proposed Solution
Add an opt-in context assembly layer that:
Acceptance Criteria
Scope and Alternatives
This is limited to local retrieval and explicitly declared dependencies. It does not generate or rewrite summaries, infer dependencies, manage all community-summary caches, delete stored vectors, or extend global/DRIFT/hybrid retrieval.
Manual post-filtering and full cache eviction remain alternatives, but do not by themselves bind selected text, summaries, and citations to the same view.
The guarantee concerns declared dependencies at assembly return—not natural-language correctness, model-answer correctness, or transactional consistency of external stores. Calls must be serialized by the application.
Impact and Related Work
Additive API, no new runtime dependencies planned. Builds on #1544, #1556, and #1675.
I am willing to contribute the implementation, regression tests, and documentation.