Signed approvals and the audit log

Editant Pro turns each approval into tamper-evident evidence: a cryptographically signed record of exactly what was approved, backed by a hash-chained audit log.

How it works

When a reviewer records a decision, Editant Pro captures a snapshot of the content and signs it. Every event is also written to an append-only audit log, where each entry is chained to the one before it, so any later alteration is detectable.

The audit log

The log lives at Editant → Audit: a newest-first table of every review event, showing the sequence number, when it happened (UTC), the event, the post, the actor and the entry’s hash. Verify chain integrity re-checks the whole chain and reports either that the chain is intact or the exact point where tampering was detected.

Filtering

• Event type matches any part of the event name, so suggestion finds every suggestion event and decision.recorded just one kind. The table narrows as you type.
• Post ID limits the table to one post.
• Seq jumps to one exact sequence number, which is what a verification report or a webhook payload refers to.

Clear removes the filters. Exports respect whatever filters are set.

Getting the evidence out

• Export log (JSON) downloads the audit log, filtered as shown, for your records.
• Export approvals (PDF) produces signed-approval certificates (filter to a post first). Each certificate includes the signed content, the signature, and a QR code linking to your site’s public verification key.