basquetWi + New ticket
movilba MOVILBA-757

Removal candidate: view agents.v_rutap_historial_carroceria_normalizacion_invariante

Done normal rmresearcher-mba-l-cc

SELECT-only 2026-10-08: this view exists only in DEV agents schema, 13 columns, currently 0 rows. Its body is a diagnostic of imported rutap.vehiculo_historial_normalizado rows with nonblank raw_carroceria and NULL carroceria_id, joined to live carrocerias for exact/ambiguous matches. PROD has no agents schema. No creation migration found in docs/tools/src, no runtime src/tools reference, no downstream pg_depend view consumer, relacl NULL; DEV lacks pg_stat_statements, so manual/external reads are unobservable. Unlike agents.v_vehiculo_lookup, this view has no explicit DEV-only migration citation and is NOT covered by MOVILBA-750 exception. Follow removal-candidate flow: seek external/manual-consumer evidence or Elazar decision; no DROP or PROD CREATE authorized from zero code/dependency evidence alone.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • db04-mba-l-ca created · 1w ago
  • db04-mba-l-ca blocked · 1w ago
    No creation migration or runtime/DB-view dependent found; manual/external reads cannot be observed from current instrumentation. Removal needs Elazar to name a consumer class worth checking or approve retirement. No DROP/CREATE on current evidence.
  • researcher-mba-l-cc note · 1w ago
    researcher-mba-l-cc 2026-10-08 19:13 ART / 22:13 UTC - collapsed into the single brief on MOVILBA-674 per coder03. See 674's note for this item's row, the full table of 14, and the one question for Elazar. Not re-measured separately here.
  • db03-mba-l-cc note · 1w ago
    db03 2026-10-09 17:21:43Z. agents schema does not exist in PROD - this view is DEV-only, confirmed via pg_namespace. Zero dependents (pg_depend). Rehearsed, then DROP VIEW agents.v_rutap_historial_carroceria_normalizacion_invariante applied DEV only. to_regclass NULL confirmed. Elazar GO via coder03, MOVILBA-674 batch.
  • db03-mba-l-cc unblocked · 1w ago
    cleared: No creation migration or runtime/DB-view dependent found; manual/external reads cannot be observed from current instrumentation. Removal needs Elazar to name a consumer class worth checking or approve retirement. No DROP/CREATE on current evidence.
  • db03-mba-l-cc completed · 1w ago
cleanup
1w ago by db04-mba-l-ca
1w ago
2026-10-09 17:22