Change one record and the check fails.
Sennit writes every step of every job into a record called the Cord. Each entry carries the fingerprint of the one before it, so a change shows up when you keep each month's fingerprint somewhere else.
What the Cord holds.
- Who ran the job, as selected, not verified.
- Which tool, and the counts: details swapped, unsure items, files not read.
- The route: which model ran each step, and where.
- The cost of each step.
- Fingerprints of the text that left and came back.
Never written to the Cord
- Job text.
- File names.
- Client names and your client list.
- Your keys.
Job text sits in a separate store on your computer. It is erased after 30 days by default. You can choose 7, 30 or 90 days, or erase a job on request, and the Cord still passes its check.
Redaction catches common patterns and your client list. It is a control with a record, not a guarantee.
What the check says.
The monthly page reads: "Unchanged since written, by its own check." The check reads every record in order and confirms each one carries the fingerprint of the one before.
That is all it can tell you on its own. Whoever holds the database could rewrite every record and link them up again, and the check would still pass. So send each month-end fingerprint to your IT provider, or anyone outside the firm, and compare it later.
Next: the fingerprint goes to your IT provider by itself. Today you send it.
Unchanged since written, by its own check. Keep each month's fingerprint somewhere else.
Share this page. Do not share job text.
The monthly page is made to be handed over: to a partner, a client, your broker or your auditor. It shows counts, routes, cost and the check. An export of the Cord can hold more than the page, so keep exports inside the firm.
If your IT provider runs it, they can see your records.
Check an export yourself.
- Export the Cord from Sennit. You get a file called sennit-cord.json.
- Download the checker, verify.py. It is one short Python 3 file that imports nothing from Sennit, so you can read all of it.
- Run it with the fingerprint you kept:
python3 verify.py sennit-cord.json --head <fingerprint>
It prints OK only if every record links to the one before and the export ends at the fingerprint you gave. If a record was changed, it names the record.