Why we built the audit log before we built the dashboard

It's tempting to build the parts of a compliance product that people click on first: the dashboard, the policy editor, the pretty charts. We built the append-only audit log before any of that existed, because every other feature in the product needed to write to it correctly from its first commit.

Retrofitting audit trails doesn't work

An audit log added after the fact only captures what someone remembered to instrument. Ours is structural: every mutation to a consent record, a policy version, or a grievance ticket passes through the same write path, so the log is a byproduct of normal operation, not a separate feature someone has to remember to call.

If proving what happened requires reconstructing it from application logs, you don't have an audit trail — you have a debugging session waiting to happen.

What this buys a Data Fiduciary

When a regulator or an internal auditor asks 'who approved this retention change, and when,' the answer needs to come from a query, not from someone's memory of a Slack thread. That's the bar we designed the log against, and it's why it shipped before the UI that displays it.