Tamper-evident verification log

planned

Keep a local, tamper-evident record of who verified a gated action, where, and when.

Every gated action will recordwho verified, which statement, which target, and

when, a local record for the question that always arrives later: “who ran that against production?”

Planned. The trail records what the connect and write gates decide, so it arrives with their native prompts, which are still being built. What ships today is the local execution log, described below.

What makes it tamper-evident

Not encryption, and not permissions - a log you can decrypt is a log you can rewrite. Each entry is chained to the one before it, so removing or editing an entry breaks the chain from that point onward. The log cannot stop someone changing it; it can make the change obvious, which is what

“evident” means here and all that a local file can honestly promise.
It is a record, not an alibi. A local log proves what this installation of SQLly saw. For a claim that holds up against a determined insider, the server's own audit is the source of truth, this is the trail that tells you where to look in it.

Stays on device

The log is a plain local file, like everything else in SQLly's configuration. It is never uploaded, never synced unless you put your SQLly folder somewhere that syncs, and readable by you without the app. Exporting it is an explicit action.

What ships today: the execution log

Every statement you run is already written to a local execution log, which you browse in Query History.

For each run it keeps the SQL, server, database, when it ran, whether it succeeded,

failed, or was cancelled, how long it took, and rows affected. String literals and comments in the stored SQL are masked, so passwords and other values typed into a query don't end up in the log. You control retention under Settings › Editor › Query History, in the Execution History Browser section:

  • Retain executions for days (0 keeps them indefinitely).
  • Maximum execution entries.
  • Cleanup runs when Query History opens. Pinned statements are stored separately and never removed by retention.

The execution log is built for finding and re-running queries, not for audit. When you run the same statement on the same server and database twice in a row, the two runs share one entry: its run count goes up and its time moves to the latest run. Retention also prunes old entries. The audit trail is designed to keep every verification as its own entry, chained to the one before.