Tessera DB
PX-01
View 07
Who wrote every record, how, and proof the trail was not edited.
Every write records who made it, through which door, when, and from which load. Security-relevant actions go to an audit trail that is hash-chained and written before the change it records.
01
03
View 07 · Audit
Every record can say where it came from.
An audit log that sits beside the database records what the application chose to tell it. This one is written by the database on every door, before the change, and chained so that an edited entry is named.
4
Facts per write
BLAKE3
Hash chain
Every
Door audited
02
03
What it does.
01
Origin on every write
On by default on every write path — insert, batch, Cypher CREATE, SQL INSERT, Bolt and HTTP. Each record carries who wrote it and through which entry point.
02
Load receipts
Each import records rows attempted, written and refused, and why. Each row names its load, and the load leads to its rows.
03
An origin card on every tier
Open a record and see who wrote it, how and from which load. The full lineage walk is on the paid tiers.
04
A hash-chained audit trail
Each entry is written before the change it records, and verifying the chain names an entry that was edited. Pro and above.
05
Content-addressed ids
A record's id is the BLAKE3 hash of its content, so a record changed under its id is detected.
03
03
Known limits.
01
Lineage lives in memory
The lineage of writes is held in memory and does not survive a restart; the audit trail and the records do.
02
Imports are one level deep
Lineage for imports and syncs is one level deep. A record-level flow needs a transform step that declares its sources.