Changelog

How to read this page

Dated, plain-language notes on what shipped, newest first. Entries describe what changed for you as a user of the product; internal refactors appear only when they change what a record can claim or how you verify one.

2026-08-25: evidence ledger hardening and pack v3.7

The access-event ledger's record hash now covers the full evidentiary row. Before this change, a ledger row's hash covered its identifier fields only, so the descriptive payload beside them was not bound into the chain; from this date every new row is hashed over the whole record, including the event details, the acting user and the recorded network address, with the canonicalisation version embedded in the hashed bytes. Existing rows still verify under the old rule, and a monotonic-version rule blocks any attempt to re-verify a tampered new row under the old, narrower hash.

Evidence packs moved to version 3.7: a pack generated for a period now explicitly asserts the network access denials that fell inside its window, and an empty window is recorded as an explicit statement that no denied attempts were recorded, rather than as silence. Timestamping requests were consolidated onto one shared RFC 3161 client with fail-closed status parsing. The public verification guide reflects all of this.

2026-08-25: audit console, network IP rules, sovereign extension states

Client workspaces gained an audit console at /app/admin/audit with three tabs: the access log with compliance exports, network access rules, and sovereign extensions. Workspace owners and admins can now restrict team sign-in to approved networks; denials and every rule change are written to a hash-chained, signed and timestamped access-event ledger. The sovereign extensions tab shows the provisioning state of client-set capabilities, including signing delegation, so what is switched where is visible rather than tribal knowledge.

2026-08-23: covenant tracker and portable verification attestations

After an envelope completes, owners and admins can record the obligations that follow from it, with due dates, reminders and an evidence trail of what was promised and what record was filed. The platform records and reminds; it makes no finding about performance. Separately, verified users can export a portable, signed attestation of their verification level that contains no personal identity documents, so a counterparty can check the level without Exedra Gate re-sharing the underlying records.

2026-08-23: dual-key attestation on envelopes

A workspace can require that two or more different team members attest an envelope with passkey signatures before it can be finalised. The attestations are recorded in the envelope's tamper-evident audit trail, carried into the evidence pack, and re-verified by the offline reference verifier.