basquetWi + New ticket
movilba MOVILBA-519

Import must not abort on missing masters (entidad/linea/catalogo)

Blocked normal dmdb04-mba-l-ca ⛔ Waiting on Eugenia for two missing-master creation facts in tracker Pendientes rows 10 (service descripcion/regimen) and 11 (new entidad tipo/nombre). Rows are written locally but online sync/answer is pending; current 5558-row book has 0 missing/ambiguous masters, so no live import is blocked. Resume design once those business fields are answered; do not infer them.

Missing masters abort the import today. Required: import creates or adds them so the DB equals the book, without reactivating soft-deleted rows (see MOVILBA-435 note 2026-09-17). 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).

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • wi-cli-venus created · 3w ago
  • coder04-mba-l-ca progress · 3w ago
    coder04-mba-l-ca | 2026-09-24 04:01 ART. Measured dev tools/rutap-snapshot-import.py:483-542: preflight still rejects missing Linea/Tipo_Servicio masters; proposed non-aborting import behavior is not implemented. Leaving backlog on parked coder03-mba-l-ca for importer/DB owner.
  • coder03-mba-l-cc assigned · 2w ago
    db03-mba-l-cc
  • coder03-mba-l-cc assigned · 2w ago
    db04-mba-l-ca
  • researcher-mba-l-cc note · 1w ago
    researcher 2026-10-08 13:19 ART: already decided - Elazar's 2026-09-19 SSOT-sync rule (snapshot makes DEV/PROD equal to it: update/add/delete, no reconciliation, only documented ssot-overrides.md exceptions) already covers this ticket's ask directly. No open choice; this is implementation backlog for the assigned db lane, not awaiting Elazar.
  • db04-mba-l-ca progress · 1w ago
    2026-10-08 SELECT-only initial census: /data-lezama/movilba/evidencia/MOVILBA-519/2026-10-08-missing-master-preflight.md. Installed importer still aborts missing/ambiguous Linea or Tipo_Servicio before staging; latest book 5558 rows has zero missing/duplicate in both PROD11 and DEV21, so current-data green is vacuous for auto-create. lineas has active-only unique numero_linea and can create a new row without reactivating retired; regimen_servicio_modalidad requires descripcion not separately stated in book, regimen_servicio_id nullable, and has no unique code constraint. Need explicit code-as-description convention and synthetic missing-master control. Projector has other catalog gates beyond line/service; enumerate before implementing whole 519. No writes.
  • db04-mba-l-ca progress · 1w ago
    MOVILBA-519 installed projector gate inventory added to /data-lezama/movilba/evidencia/MOVILBA-519/2026-10-08-missing-master-preflight.md. The request spans vehicle, entidad, linea, service modality, tramite/propulsion/piso/emissions options, subtype, manufacturer, eight binary fields, plus pending chassis and invalid numeric consumo; these are not all missing-master cases. Current snapshot has 0 missing/duplicate line/service in both bases, so auto-create path remains unexercised. A blanket skip-gate would silently conflate absent catalog rows with malformed source and unapproved chassis equivalences. Next implementation needs per-field creation contracts and synthetic missing-master controls; no write.
  • db04-mba-l-ca progress · 1w ago
    Further SELECT-only PROD check: seven live regimen_servicio_modalidad codes have descriptions that are sometimes the code, sometimes expanded/qualified; all seven have non-NULL regimen_servicio_id (six id 4, one id 3). The workbook supplies only Tipo_Servicio code, so it cannot determine either required descripcion or business regimen for a NEW code. Auto-creating that master requires an explicit placeholder convention (e.g. code-as-description and NULL regimen), not a silent inference from existing rows. Evidence updated: /data-lezama/movilba/evidencia/MOVILBA-519/2026-10-08-missing-master-preflight.md. No DB write.
  • coder03-mba-l-cc statusChanged · 1w ago
    coder03-mba-l-cc 19:33Z - promoted for db04, whose only other actionable item (490) is stopped behind db03's projector lock. No lane sits idle behind a lock.
  • db04-mba-l-ca progress · 1w ago
    SELECT-only current-book census PROD then DEV: snapshot 11/21, same MD5 eb2e2683, 5558 Base rows each; normalized 5558/5558 resuelto, 0 unresolved across 21 mapped classes. Direct live cardinality for entidad/linea/tipo_servicio: 0 missing and 0 ambiguous in each base. Installed Python preflight aborts entire batch before staging for missing OR ambiguous Linea/Tipo_Servicio; materializer also aborts cardinality !=1 before DML; projector records other conflicts and later apply can rollback. Current zero is vacuous for the requested missing-master create path. Genuine ambiguity remains blocking, while a 0-match master needs field-specific creation rules; service workbook has no required descripcion/regimen to infer. No write and no importer/projector edit while MOVILBA-340/490/367 sequence holds. Query and report: /data-lezama/movilba/evidencia/MOVILBA-519/2026-10-08-current-master-cardinality-PROD-Y-DEV.sql and 2026-10-08-current-snapshot-abort-inventory.md. Next: define per-master creation policy and rollback-only synthetic missing-master control.
  • db04-mba-l-ca progress · 1w ago
    Rollback-only failing-before fixture observed in BOTH PROD then DEV against installed validar_linea_tipo_servicio: baseline passes; absent Linea aborts with Linea no resuelve en el catalogo; absent Tipo_Servicio aborts with Tipo_Servicio no resuelve en el catalogo; closed-period ambiguous Linea aborts with Linea resuelve 2 veces en el catalogo; ambiguous Tipo_Servicio aborts with Tipo_Servicio resuelve 2 veces en el catalogo. Each raises SystemExit before staging, whole import blocked. BEGIN READ ONLY/ROLLBACK, synthetic workbook row plus SQL UNION ALL synthetic catalog return rows, no DB DML or repo edit. Exact output/stage and reusable fixture: /data-lezama/movilba/evidencia/MOVILBA-519/2026-10-08-preflight-abort-observed-PROD-Y-DEV.md. Stakeholder question: book has only service code, not required descripcion or regimen; Eugenia must specify values or supply them before creating a missing service master. No implementation until 340->490->367 sequencing clears.
  • coder03-mba-l-cc note · 1w ago
    Pregunta ESCRITA en el tracker por coder03-mba-l-cc, 2026-10-08 16:45 ART, hoja Pendientes fila 10 (max_row reportaba 17 y miente; las filas no vacias pasaron de 8 a 9). Columnas escritas: bwi=MOVILBA-519, Para=Eugenia, Pregunta, Donde mirar, Nuestra respuesta, fecha de inicio=08/10/2026 como TEXTO con number_format @, Estado=Pendiente, Estado_comentario. La columna de respuesta de la interesada quedo vacia, verificado al reabrir el archivo guardado. Snapshot de las 9 columnas que el script escribe MAS la columna de respuesta, aserido fila por fila antes del save: cero celdas ajenas tocadas. Copia con timestamp en archivo/ antes y copia estampada 2026-10-08-1645 al lado despues. Lock del hub sobre rutap-tracker.xlsx tomado y liberado. Estado=Pendiente y no Bloqueado, a proposito: db04 midio 0 codigos de Tipo_Servicio sin resolver y 0 ambiguos en PROD y DEV sobre el snapshot pinneado (11 en PROD, 21 en DEV, mismo MD5 eb2e2683, 5558 filas cada uno), asi que la pregunta no frena ninguna fila del libro vigente. El detalle de eso va en Estado_comentario, que es donde vive el matiz: Estado es UNA palabra del conjunto cerrado. ESCRITO NO ES PREGUNTADO. El archivo en disco correcto no significa que Eugenia lo haya visto: la copia online es un paso aparte y hasta que sincronice la pregunta existe para nosotros y no para ella.
  • db04-mba-l-ca progress · 1w ago
    Coder03 confirms the service-master question is WRITTEN in the agent-maintained tracker, Pendientes row 10, Estado Pendiente; it has NOT been asked/answered in the online copy. Current pinned snapshot has 0 missing/ambiguous line/service/entity rows, so no live row waits on it. The PROD+DEV failing-before fixture is complete, but creation semantics for a new Tipo_Servicio remain unapproved because the workbook lacks required descripcion and regimen. Do not implement a code-as-description placeholder or claim row 10 resolved. Next: wait for Eugenia reply and preserve the fixture as the failing-before control.
  • db04-mba-l-ca progress · 1w ago
    Read-only creation-boundary design completed while 340 projector lock remains: /data-lezama/movilba/evidencia/MOVILBA-519/2026-10-08-creation-cutover-design-boundaries.md, with reproducible PROD->DEV census SQL. Importer advisory transaction currently runs line/service preflight BEFORE duplicate-digest check; any future master writes belong after header+duplicate validation and before materializer/projector, same transaction, with absent/ambiguous outcomes separate and post-write exact-one gate. Linea: active partial unique key; PROD 30/DEV 26 retired-only numbers, none on current open book rows, but future closed-history ambiguity if a new active sibling is made. Entidad: 25 source CUITs use two actual tipo_entidad IDs (24 SA, 1 CAPITAL_MIXTO); two CUITs have multiple empresa text spellings, so new CUIT cannot derive type/name blindly. Service: 7 active codes, all regimen populated, 5 descriptions differ from code, so no payload from workbook alone; Eugenia row 10 remains written-not-asked. No DB/catalog write, no code edit, no unauthorized placeholder.
  • db04-mba-l-ca progress · 1w ago
    Separate entidad-master question sent to coder03 for Eugenia tracker, not merged with service row 10: when the book first names a CUIT absent from public.entidades, which exact tipo_entidad and display nombre should MovilBA create? Current 25 source CUITs map to 24 SA plus 1 CAPITAL_MIXTO, and 2 CUITs have multiple identificador_empresa spellings; a universal type or arbitrary period-name choice is unsupported. No writer/DB change; current book has 0 missing entidad rows.
  • coder03-mba-l-cc note · 1w ago
    Segunda pregunta ESCRITA en el tracker por coder03-mba-l-cc, 2026-10-08 17:13 ART, hoja Pendientes fila 11. Las dos filas de MOVILBA-519 conviven: la 10 es la del tipo de servicio y la 11 es la de la entidad; el script aserto que existia EXACTAMENTE una fila previa de 519 y que su texto mencionaba Tipo_Servicio antes de escribir, y despues del save reabrio el archivo y verifico que la 10 sigue intacta. Snapshot de las 9 columnas escritas mas la columna de respuesta de la interesada, aserido fila por fila antes del save: cero celdas ajenas tocadas. La columna de respuesta de la fila nueva quedo vacia. Copia con timestamp en archivo/ antes y copia estampada 2026-10-08-1713 al lado despues. Lock del hub tomado y liberado. Contenido: cuando el libro trae un CUIT que todavia no es entidad, faltan DOS datos que el libro no informa - el tipo de entidad y el nombre a mostrar. Medicion de db04 que justifica preguntar en vez de elegir: los 25 CUIT del libro ya existen como entidad, pero se reparten entre 24 SA y 1 CAPITAL_MIXTO, y dos CUIT figuran con mas de una grafia de empresa. Deducir cualquiera de los dos campos se equivoca en algun caso y queda escrito en la base. Estado=Pendiente, igual que la 10 y por la misma razon medida: no bloquea ninguna fila del libro vigente. ESCRITO NO ES PREGUNTADO - la copia online es un paso aparte y hasta que sincronice las dos preguntas existen para nosotros y no para Eugenia.
  • db04-mba-l-ca blocked · 1w ago
    Waiting on Eugenia for two missing-master creation facts in tracker Pendientes rows 10 (service descripcion/regimen) and 11 (new entidad tipo/nombre). Rows are written locally but online sync/answer is pending; current 5558-row book has 0 missing/ambiguous masters, so no live import is blocked. Resume design once those business fields are answered; do not infer them.
bug
3w ago by wi-cli-venus
1w ago