Skip to the card

Card 063 of 10002026-08-25 issue

Observed arrival · 2026-08-25

The Audit Log Page

auditlog.dev Observed source
Editorial interest 84/100 Selection signal · not a rating of the site

A five-part technical essay about designing product audit logs for the auditor who must reconstruct events long after they happened.

Landing page captured for the 2026-08-25 issue.

Field notes

The essay treats an audit trail as an application product surface rather than infrastructure exhaust. Its example schema separates occurred_at from recorded_at, preserves actor snapshots, records allowed and denied outcomes, and stores narrowed before-and-after values for changes. A shared set of 43 events links the opening schema discussion to later evidence questions, while examples cover role changes, erasure, API activity, agents, impersonation, and HTTP telemetry.

Observed signals

Read the marks

Editorial observations of this landing page, not a rating.

LoginAccess appeared gated
PrettyNotable craft visible
ProPolished or operationally mature
NicheUnusually specific use
ƒJavaScriptBrowser-side code central

One card from the complete issue

Thirty-One Wells, Not Four

295,249 arrived 1,000 judged 1000 catalogued Enter the complete issue
auditlog.dev

Landing page observed 2026-08-25. The live site may have changed.