Repository navigation
Audit-event export and retention enforcement #33
Description
GET /v1/audit-events already supports filtering by target, actor, action, application, organization, tenant, and time range, and the audit-archive job runs. What's missing is a compliance export and retention-policy enforcement visible through the API.
Spec: Roadmap → Phase 3 ("Richer audit/compliance views: filtering, export, retention policy enforcement"), Compliance.
Trigger: a SOC 2 audit, or a customer's data or audit export request. Don't build it ahead of either.
Scope:
- An export endpoint, likely asynchronous: filtered audit events as NDJSON or CSV, delivered as a presigned S3 URL
- Retention policy enforcement and its documentation (what's purged or archived, and when)
- A permission for export, separate from read
- OpenAPI, MCP, tests, and the Changelog
- Also resolve open Decision Move the API version from the URL to a Substratal-Version header #37 (audit-log immutability), since export depends on the same guarantees
Activity
Adron commentedon Oct 22, 2026
The management console needs a minimum audit-export shape; it's written up in #56 ([api-gaps] G19) so this issue can satisfy both. Closing #56 when this closes.
Adron commentedon Oct 22, 2026
Built in #61 (export endpoints, worker, S3 storage, audit.exported; retention was already enforced by the hot window + archival). Decision #37 is left open — export doesn't depend on it.