# Bitemporal claim provenance > Source-anchored research for Bitemporal claim provenance. Run status: BUDGET_EXHAUSTED. Parent: [Concept knowledge architecture strategies](https://llms-explorer.com/tree/concept-knowledge-architecture-strategies/) · 3 facets · 15 facts · page: https://llms-explorer.com/tree/bitemporal-claim-provenance/ ## How it works - Bitemporal history separates when a fact applies in the modeled world from when the system recorded it. (medium confidence) — [source](https://docs.xtdb.com/about/time-in-xtdb.html) ## Comparisons and alternatives - PROV validity checks a consistent provenance history rather than establishing the factual truth of its assertions. (low confidence) — [source](https://www.w3.org/TR/prov-constraints/) ## Facts and statements - PROV represents a revised document as an entity derived from an earlier document entity. (medium confidence) — [source](https://www.w3.org/TR/prov-dm/) - A retrospective correction changes the current account of valid history while preserving earlier recorded beliefs. (medium confidence) — [source](https://docs.xtdb.com/about/time-in-xtdb.html) - Valid time can describe a future-effective change recorded before that change takes effect. (low confidence) — [source](https://docs.xtdb.com/about/time-in-xtdb.html) - 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](https://docs.xtdb.com/about/time-in-xtdb.html) - An audit query can select a past system time to exclude corrections learned later. (low confidence) — [source](https://docs.xtdb.com/about/time-in-xtdb.html) - PROV entities have fixed aspects; changing an aspect can require a different entity. (medium confidence) — [source](https://www.w3.org/TR/prov-dm/) - The temporal database glossary distinguishes uncertain valid time from transaction time maintained by the database. (low confidence) — [source](https://www2.cs.arizona.edu/~rts/pubs/TRmerged.pdf) - A fact transferred between databases can carry several transaction-time histories. (low confidence) — [source](https://www2.cs.arizona.edu/~rts/pubs/TRmerged.pdf) - Different modeled perspectives can assign different valid times to the same fact. (low confidence) — [source](https://www2.cs.arizona.edu/~rts/pubs/TRmerged.pdf) - XTDB v1's bitemporality does not itself implement persisted-query replay and cascading retroactive corrections. (low confidence) — [source](https://v1-docs.xtdb.com/concepts/bitemporality/) - An immutable record of an action's inputs can satisfy some audit needs without a complete bitemporal property history. (low confidence) — [source](https://martinfowler.com/articles/bitemporal-history.html) - PROV quotation describes copied content, whereas revision describes a revised version of an earlier entity. (low confidence) — [source](https://www.w3.org/TR/prov-dm/) - 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](https://docs.xtdb.com/quickstart/sql-overview.html)