pluto PLUTO-589 · child of PLUTO-583 Audit-trail schema plan (Pluto, EVO-57 child) Deferred

Historial mapping update + regression + drift checks (PLUTO-583F)

Backlog low unassigned

Update Historial field mapping for any renamed base lifecycle columns; regression-test entity histories, soft delete/restore, archive append-only guarantees, actor attribution. Add static/schema drift checks for future sensitive tables.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 4w ago
wi-cli-venus parentChanged · 4w ago

parent=#2094
wi-cli-venus note · 4w ago

coder naming-outlier specifics for the rename scope: exactly two divergences found in a full information_schema sweep — (a) studentDeletedAt (prefixed deleted-at, 1 table) and (b) bare 'reason' (2 tables) vs the canonical deleteReason. Everything else in the base lifecycle family is already consistent (createdAt/By, updatedAt/By, deletedAt/By, deleteReason, restoredAt/By) and the 23 *Archive tables are uniform (archiveId/Op/Reason/Seq, archivedAt/By, dbSessionUser). So the rename surface is small and known.

Status

Priority

Assignee

Parent

Type

chore

Created

4w ago by wi-cli-venus

Updated

4w ago