Libro: 2 pares motor_nro truncado (AG358KX, AE168VP) - pregunta al tracker de Eugenia

Sub-tickets

Activity

• db03-mba-l-cc created · 1w ago
• db03-mba-l-cc progress · 1w ago
  db03-mba-l-cc 2026-10-07: written to live tracker (todo-rutap-importacion-prestaciones.xlsx, Pendientes row 60), sqlite snapshot 38. Protocol followed: hub lock, timestamped backup (archived/todo-rutap-importacion-prestaciones.xlsx.bak-20261007-1211), header/identity assert, column F (stakeholder answer) unchanged-assert across all 39 prior rows, reopened+reverified post-save. Written, not yet asked (Elazar copies to the online copy separately). Holding backlog pending Eugenia's answer.
• db03-mba-l-cc progress · 1w ago
  db03-mba-l-cc 2026-10-07: verification found the premise WRONG, not a genuine Eugenia question. Re-checked rutap.vehiculo_historial_normalizado (live, snapshot 11) for both vehiculos: the two motor_nro values are NOT simultaneous/conflicting - they are sequential, non-overlapping periods, each faithfully imported with its own period-accurate value. AG358KX: '926996U1394956' (14) covers 2025-07-08 through 2026-03-09 (4 periods); '26996U1394956' (13) covers 2026-03-09 onward (2 periods, including the current open one). A later book-recorded change, already correctly split by period - exactly the designed temporal model, not a contradiction. AE168VP: '924996U1288635' (14) covers 2025-07-08..2025-07-23 (closed); '924996U128863' (13) covers 2025-09-16 onward (open, current). Same pattern. Original ticket mis-stated fila 4506/AG358KX as carrying the 14-char value and called it VIGENTE - live data shows fila 4506 (and 2799) carry the 13-char value, and THAT is the vigente one. No ambiguity to resolve, no decision needed from Eugenia - withdrawing the tracker question, moving to Resueltos as no-reproducido/false-premise.
• db03-mba-l-cc completed · 1w ago
  withdrawn: db03-mba-l-cc 2026-10-07, verification found the premise wrong - not a genuine question, moved to tracker Resueltos (row 144), sqlite snapshot taken. See progress note for full finding.
• coder03-mba-l-cc note · 1w ago
  Tracker canon Resueltos row has compound Estado 'Retirada - premisa incorrecta'; per the one-word rule it must become Estado=Retirada, Estado_comentario='premisa incorrecta' on the next tracker write.
• coder03-mba-l-cc note · 1w ago
  coder03 11:12 ART: Resueltos Estado split done: Estado=Retirada, Estado_comentario='premisa incorrecta - ...'. Archive archived/2026-10-08-1111-pre-720-*.xlsx, after-copy 2026-10-08-1111-todo-rutap-importacion-prestaciones.xlsx. No compound Estado left in Resueltos. Awaiting sqlite snapshot import by db03.