Catalogo chasis: la fila 46/144 (FU-BMO 368 VERSION 1721 L62 CA) resuelve por el resolver a 116 - AF178SI
db03-mba-l-cc 2026-09-24 06:55 -03 - found while measuring MOVILBA-574. Catalog row chasis 46 (DEV) / 144 (PROD): fabricante MERCEDES BENZ, chasis_modelo 'FU-BMO 368 VERSION 1721 L62 CA', 1 live vehicle (AF178SI). The rutap.chasis_resolver maps that exact label spelling (MERCEDES BENZ, FU-BMO 368 VERSION 1721 L62 CA, up 124) to chasis 116 ('OH 1721 L-SB/62', 288 live vehicles), not to the row that carries the label. The book spelling for AF178SI, 'FU-BMO 368 VERSION 1', resolves to 46/144. So the catalog has a row whose own label resolves to a different chassis: either 46/144 is a duplicate of 116 (and AF178SI should point at 116) or the resolver entry for the label spelling is wrong. Not decided - needs the manufacturer designation check (docs/reference/chasis-equivalencias.md rules: triple key, equivalences only within a fixed manufacturer). Ids differ per base, label is the comparable. Evidence: /data-lezama/movilba/evidencia/MOVILBA-574/574b-DEV.out and 574b-PROD.out section 2b. Read-only, nothing changed. Not checked against the 2026-09-24 book (bases on snapshot 2026-09-19-0648).
Activity
-
db03-mba-l-cc
-
db04-mba-l-ca
-
Eugenia contesto las preguntas 1 y 2, 2026-10-01, con el mismo texto para las dos: 'Edu mando un documento con el formato del catalogo correspondiente con lo que tiene CNRT, debemos ajustarlo a ese manual. Si quieren lo vemos con el archivo y con Elazar.' No es todavia una equivalencia para AF178SI: el catalogo de chasis se alinea al manual de CNRT que mando Edu. Falta conseguir ese archivo - no esta en /data-lezama - antes de poder resolver el mapeo.
-
Stakeholder feedback, tracker online 2026-10-05 13:24 (Eugenia/Fabri), relayed by coder03: Row AF178SI: 'Lean > Verificado, figura correcto: FU-BMO 368 VERSION 1721 L62 CA'. Row CNRT file: 'Ya te lo enviamos, pero recorda que debe ser mas manual que predefinido.' Verificado: 'CHEQUEAR'.
-
2026-10-05 SELECT-only PROD snapshot8 (2026-09-30 book): AF178SI vehicle6028 and both normalized periods (filas3513/5303) already point to chasis144, catalog label 'FU-BMO 368 VERSION 1721 L62 CA', matching stakeholder verification; raw book abbreviation 'FU-BMO 368 VERSION 1' is preserved. The resolver key for that abbreviation maps to144. Separate original defect remains: exact key (MERCEDES BENZ,FU-BMO 368 VERSION 1721 L62 CA,GO id124) maps to chasis116 ('OH 1721 L-SB/62'), while catalog row144 bears the key's own label. That exact full string occurs in 3 current-book rows, all AB068XE (filas2810/3398/5316), currently linked to116; same AB068XE VIN 8AB368187? [see live query] has two earlier book periods raw 'OH 1721 L-SB/62' also linked to116. Therefore globally remapping the key to144 would alter another vehicle's three history periods/current link, not just AF178SI. No write until the equivalence/AB068XE scope is resolved; AF178SI itself needs none.
-
Correction to preceding progress event: AB068XE VIN is 8AB368187HA146563 (not the placeholder '[see live query]'). All five current-book rows for AB068XE share this exact VIN. No DB write.
-
Domain-scoped override drafted: rutap.v_rutap_chasis_resuelto returns catalog chassis 144 only for AF178SI under MERCEDES BENZ/GO and the two FU-BMO spellings; global resolver remains 116 and AB068XE's five rows remain 116. Draft SQL: /data-lezama/movilba/migration-evidence/2026-10-05-movilba-578-af178si-chasis-override-PROD-Y-DEV.sql. ROLLBACK rehearsals passed on PROD and DEV: AF178SI two rows=144, AB068XE five=116, 5546 non-target rows full-row equal. docs/reference/ssot-overrides.md updated. No apply yet; sent to audit.
-
Scoped override draft and documentation are in audit; PROD/DEV rehearsal passed under ROLLBACK, no apply yet.
-
audit pass: SQL+ssot-overrides.md diff, full read
payload
{"scope":"SQL+ssot-overrides.md diff, full read","outcome":"pass","evidence":"self-verifying pre/post checks, byte-equal non-target rows, resolver untouched; DB EXECUTION NOT PERFORMED BY AUDIT","reportRef":null} -
Applied audited SHA256 755e4899a4f6a379467d3fae3e519e5bccb121df44a0621a3d7a16e40be299e4 to PROD then DEV (both COMMIT). Installed viewdef md5 is 90d16e82fd83d8c23bb292cf6f3f51c2 on both; post-apply SELECTs: AF178SI 2/2 ->144, AB068XE 5/5 ->116, global full-label resolver remains 116. Migration moved byte-identically into docs/migrations; README row and DEV introspection mirror added. Final repository diff sent to audit before SHIP.
-
audit pass: post-apply repo diff: migrations/*.sql, README.md, ssot-overrides.md, schema.ts
payload
{"scope":"post-apply repo diff: migrations/*.sql, README.md, ssot-overrides.md, schema.ts","outcome":"pass","evidence":"SHA 755e4899 matches audited file; schema.ts single hunk matches exact CASE fragment; relations.ts unchanged; README row added","reportRef":null} -
Override for AF178SI is applied PROD then DEV and shipped in v5.6.160; audited migration SHA256 755e4899, installed viewdef md5 90d16e82 on both; post-apply AF178SI resolves 144 and AB068XE remains 116. PROD/DEV/pod now serve later patch 161. No remaining work under 578.