# Audit trail events for SaaS ops: append-only who-did-what you can query

When support asks “who changed this plan?”, noisy app logs rarely answer. They show request latency, stack traces, and correlation IDs — useful for triage, weak for accountability. After you leave a Lovable or Bolt sandbox and run SaaS ops on an app you own, you need an **append-only audit trail**: immutable events that record actor, action, resource, outcome, and correlation so humans and agents can reconstruct what changed without guessing.

This post is about a queryable **audit event store**, not a logging tutorial. Pair it with [structured production logs](/blog/production-structured-logging-for-agents) for runtime triage; keep the two stores separate.

---

*This is an excerpt. Read the full post at [otf-kit.dev/blog/audit-trail-events-saas-ops](https://otf-kit.dev/blog/audit-trail-events-saas-ops) — full-stack kits your AI coding agent can actually ship to production. [Browse the kits →](https://otf-kit.dev)*