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.
AT RECORDED reads the graph as it was recorded at a past moment. You do not build a separate temporal layer, a snapshot store, or an event-log replay.
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.
Each committed node and relationship write records the SHA-256 hash of the previous record. GET /graphs/{name}/audit/verify re-hashes the history log from the first record and reports the first broken record, if any. The log is not signed, so the check does not detect a rewrite of the whole log, or removal of the most recent records, by someone with write access to the server.
Per-subject encryption keys and key destruction are in development. Contact us before relying on them for erasure requests.