Drag the scrubber. The database reconstructs what was known at that exact instant — not what's known today, not the policy after the change. This is bitemporal AT RECORDED in one Cypher line. The query never changes; only the date does.
Every other database makes you build a custom temporal layer, run ETL into a snapshot store, or reconstruct from event logs — with no integrity guarantees and weeks of engineering time. InvariantDB has it native.
Same MATCH (p:Policy) RETURN count(p). Only the AT RECORDED timestamp moves. The engine handles the rest.
The result at March 5 contains nothing that was learned after March 5. Train agents on past decisions without leaking future data.
The history isn't trusted because we say so — it's cryptographically signed. db.verifyAclChain() proves it back to genesis.
One key destroyed — subject's PII unreadable across every snapshot, the audit chain still verifies. GDPR Article 17 and SOX retention, compatible.