mars MARS-492 · child of EVO-57 Audit-trail schema normalization (coverage + field-name naming), planned per-project Deferred

EVO-57 Mars: audit-trail schema normalization plan (coverage + naming)

Blocked normal cmcoder03-mars-ca ⛔ Elazar re-scope GO per pm-mars-cc 2026-09-11: no justification for extra tables/code, finetune/minimize; every audit-twin column needs per-table justification and archive twins need a fleet PII-retention ruling. Blocked independently of MARS-483's delivery - do not queue on the strength of the dependency alone. pm-mars-cc tracks it in the open-decisions file and is not re-asking Elazar. Supersedes my earlier note on this item, which read it as merely unplaced.

Per EVO-57: plan (not build) audit-trail schema normalization for Mars — (A) coverage: createdBy/At+deletedBy/At+changelog/archive on SENSITIVE-data tables only (Elazar ruling #5a exempts telemetry/queue/non-sensitive), using MARS-483's completed gap report as input; (B) naming: normalize all audit/soft-delete/changelog/historial field names to one convention, integrating existing Historial pattern (MARS-410) not duplicating it. Deliverable = plan only (approach + migration sequencing), no DDL. Build WITH coder-mars-cc+db-mars-cc+audit-mars-ca, file child bwis as needed, report bwi ref + outline to pmmaster-evolutiva-cc.

Sub-tickets — 0/5 done

WP1 naming: deletedBy -> deletedByUserId dual-column shim

MARS-493 Deferred

dmdb03-mars-ca

WP2+WP3: add deletedByUserId + createdByUserId coverage columns

MARS-494 Deferred

dmdb03-mars-ca

WP4a: archive twins + triggers for userRoles + lookupOptions

MARS-495 Deferred

dmdb03-mars-ca

WP4b: archive twins + triggers for supportTickets/Messages/NotifySubscriptions + accessRequests + accountSwitchLinks

MARS-496 Deferred

dmdb03-mars-ca

WP4c: archive twins + triggers for practicaReviews + practicaComentarios + studentPostgradoProgression

MARS-497 Deferred

dmdb03-mars-ca

+ Add sub-ticket

Activity

wi-cli-venus created · 2026-07-17

parent=#2093
wi-cli-venus statusChanged · 2026-07-17

status=backlog
wi-cli-venus assigned · 2026-07-17

--body
wi-cli-venus commented · 2026-07-17

--body
wi-cli-venus statusChanged · 2026-07-17

HOLD — Elazar re-scope 2026-07-17: no blanket coverage, per-table justification required, DEFERRED, no release GO. Do not execute as drafted.
wi-cli-venus note · 5w ago

Input dependency now available (db-mars-cc, 2026-09-11). MARS-483, the createdBy/deletedBy/changelog coverage audit that this plan takes as input, is closed done - its Phase-1 gap report is in that item's events and was re-verified against the live catalog today: of 43 base tables in public, zero carry a createdBy column and 9 carry deletedBy. Leaving this item untouched otherwise: it is assignedRole=pm and the plan is not the DB lane's to write or to cancel.
wi-cli-venus blocked · 5w ago

Elazar re-scope GO per pm-mars-cc 2026-09-11: no justification for extra tables/code, finetune/minimize; every audit-twin column needs per-table justification and archive twins need a fleet PII-retention ruling. Blocked independently of MARS-483's delivery - do not queue on the strength of the dependency alone. pm-mars-cc tracks it in the open-decisions file and is not re-asking Elazar. Supersedes my earlier note on this item, which read it as merely unplaced.
wi-cli-venus note · 5w ago

Retired-referent fix, not a scope change. The blockedReason named pm-mars-cc as the agent tracking this in the open-decisions file. That seat does not exist - Elazar collapsed Mars to three agents on 2026-09-11 and I hold the PM seat alongside the coder lane. A WI blocked on a retired agent is the one surface that fails toward LOOKING LIKE WORK IN PROGRESS rather than toward absent, so it can never unblock and nothing signals that. I am the tracker; the block itself stands unchanged, and it still needs Elazar on two things: per-table justification for every audit-twin column, and a fleet PII-retention ruling before archive twins. Same sweep, same reason, six items reassigned off names that are no longer on the roster: MARS-467, MARS-97, MARS-35, MARS-444, MARS-534 (all pm-mars-cc) to me, and MARS-612 (coder03-mars-ca, a lane that does not exist) to coder02-mars-cc as scoped UI/validation work. Per the commons triage rule these are REASSIGNMENTS: a retired assignee establishes that nobody CAN do the work, never that nobody SHOULD, so none of them is closed or canceled and no scope was touched. MARS-482 keeps pm-pluto-cc - that is another project's live lane, not a Mars referent. Still owed on this sweep: the retired referent lives in title/description/stated-dependency as often as in assignedAgent, and MARS-97's description names audit-mars-ca as the owner of stages 1 and 6. That is a description edit, not an assignment, and it is not done yet.
wi-cli-venus assigned · 5w ago

coder-mars-cc
wi-cli-venus assigned · 4w ago

coder03-mars-ca