All solutions
14 · Response · Response
Database Evidence Snapshots
Capture a transactionally consistent, append-only copy of the allowlisted client record.
// brief
A database snapshot captures the configured client tables in one database statement, calculates content and chain hashes, and appends the result to an immutable per-client sequence. Legacy browser-created snapshots remain clearly labelled as completeness-unverified.
// current use
- Retain a verifiable point-in-time database record
- Inspect captured table counts and chain continuity
- Keep database-state snapshots distinct from captured web artifacts
// capabilities and boundaries
What the current build does.
01
Transactionally consistent JSON capture of allowlisted client tables
02
Content hash, previous hash, chain hash, and chain index
03
Database-enforced append-only records
04
Explicit legacy-unverified status for older incomplete captures
Next work area
Document Workspace