Lifecycle Evidence and Removal Capture

Context

Removal must retain its own decision evidence without generating downstream work about disappearing records. Existing history and audit mechanisms have different ownership.

Decision

Keep lifecycle evidence in its domain and job records, and suppress business-record change capture where removal implementations declare that behavior.

Alternatives Considered

Write record-history revisions for lifecycle changes: History written onto destroyed records would need removal too and would not retain the deletion account. Let purges emit change events: Downstream processing could act on records the purge is removing.

Consequences

Jobs, requests, notices and load facts provide lifecycle attribution alongside record bookkeeping. Ordinary business-standing changes do not currently append a security audit event.