movilba
MOVILBA-522
PROD: 2407 legacy_unknown rows block delete-by-absence (needs own GO)
Done normal
dmdb02-mba-l-ca
Deleting legacy_unknown rows absent from the book in PROD is a DELETE and needs a fresh explicit GO via coder03-ca. Depends on the origin-agnostic delete ticket. Elazar rule 2026-09-19: a new SSOT snapshot makes DEV and PROD equal to it (update/add/delete), no reconciliation, no who-wins evaluation; only documented Eugenia-agreed overrides (docs/reference/ssot-overrides.md). Measured by coder03-ca, db02-ca, audit-ca on the installed import (bodies identical in DEV and PROD, 486).
Activity
-
PROD current-state measurement: snapshot 5 has 2413 current distinct vehicles and public.vehiculos has the same 2413. Origin-agnostic reconciliar_snapshot(5,false) reports 0 absent-book candidates, 0 duplicates, 0 changes, 0 gate failures. The 2407 legacy_unknown rows are snapshot-backed; provenance is not deletion eligibility. Explicit ROLLBACK and fresh unchanged proof. Evidence: /data-lezama/movilba-web/evidence/2026-09-20-movilba-522-prod-current-state-db02-mba-l-ca.md
-
Obsolete premise: all 2407 legacy_unknown vehicles are present in snapshot 5. Installed origin-agnostic reconciliation finds zero delete candidates and zero changes. No PROD write needed; evidence recorded.
-
Independent evidence review PASS: durable SHA256 02eabf0dfa5da97b521edb98bd3db3e92ff3f3c210a7eee1a74ae86ab9b70bcd matches; snapshot/current denominators are 2,413=2,413, origin-agnostic installed reconciler returns 0 absent-book, 0 duplicate, 0 field-change, and 0 gate-failure candidates under apply=false; explicit ROLLBACK and fresh unchanged 2,413 proof are recorded. Closing as obsolete is correct; legacy_unknown is provenance, not deletion eligibility.
bug
3w ago by wi-cli-venus
3w ago
2026-09-20 05:54