Bitemporal claim provenance
Parent: Concept knowledge architecture strategies · Published reference · snapshot 2026-10-22
↓ Facts as markdownall context files
Source-anchored research for Bitemporal claim provenance. Run status: BUDGET_EXHAUSTED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
How it works
- Bitemporal history separates when a fact applies in the modeled world from when the system recorded it. (medium confidence) [source]
Comparisons and alternatives
- PROV validity checks a consistent provenance history rather than establishing the factual truth of its assertions. (low confidence) [source]
Facts and statements
- PROV represents a revised document as an entity derived from an earlier document entity. (medium confidence) [source]
- A retrospective correction changes the current account of valid history while preserving earlier recorded beliefs. (medium confidence) [source]
- Valid time can describe a future-effective change recorded before that change takes effect. (low confidence) [source]
- XTDB's ordinary query defaults to current valid time and the best currently known system-time view. (low confidence) (verified as of 2026-10-22) [source]
- An audit query can select a past system time to exclude corrections learned later. (low confidence) [source]
- PROV entities have fixed aspects; changing an aspect can require a different entity. (medium confidence) [source]
- The temporal database glossary distinguishes uncertain valid time from transaction time maintained by the database. (low confidence) [source]
- A fact transferred between databases can carry several transaction-time histories. (low confidence) [source]
- Different modeled perspectives can assign different valid times to the same fact. (low confidence) [source]
- XTDB v1's bitemporality does not itself implement persisted-query replay and cascading retroactive corrections. (low confidence) [source]
- An immutable record of an action's inputs can satisfy some audit needs without a complete bitemporal property history. (low confidence) [source]
- PROV quotation describes copied content, whereas revision describes a revised version of an earlier entity. (low confidence) [source]
- XTDB provides ERASE for hard deletion of history; ordinary historical retention is therefore not an unconditional permanence guarantee. (low confidence) (verified as of 2026-10-22) [source]
Children
- Temporal dependency invalidation (frontier)
- Uncertain temporal intervals (frontier)
- Evidence-source identity and ownership (frontier)
Frontier under this node: Evidence-source identity and ownership, Temporal dependency invalidation, Uncertain temporal intervals