Skip to content

Events-table retention/prune policy (deferred by ADR-032/041/094/103) #730

Description

@ohdearquant

Problem

The events table grows without bound. Four ADRs now record the retention/prune question as open and deferred:

  • ADR-032 and ADR-041 defer it at the event-plane design layer
  • ADR-094 §5 defers it while adding lifecycle-telemetry variants
  • ADR-103 adds a small bounded increment (phase-span rows + payload enrichment) and again defers it

Every deferral has been individually reasonable; collectively there is still no policy, and the audit stream is written on every verb dispatch.

Ask

A retention/prune decision for the events table: retention window(s) per EventKind class (audit vs lifecycle vs phase-span), the prune mechanism (curation-layer verb vs background maintenance pass), and its WAL interaction (prune is itself a write burst; must respect the ADR-091 checkpoint doctrine).

Sequencing

Deliberately scheduled AFTER ADR-103 Stage 1 telemetry exists: retention windows should be chosen against measured event-volume and read-pattern data, not guessed (instrument-before-enforcement, same doctrine as ADR-091 and ADR-103 Stage 2).

Non-goals

Not a schema change proposal; whatever lands must be a policy + mechanism over the existing table.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions