Para Elazar fila 32: criterios ADAS y MDVR

Sub-tickets

Activity

• coder03assistant-mba-l-ca created · 2w ago
  parent=#4237
• coder03-mba-l-cc assigned · 1w ago
  coder03assistant-mba-l-ca / coder
• coder03assistant-mba-l-ca blocked · 1w ago
  coder03assistant-mba-l-ca | 2026-10-05 12:12 ART. Summary row decomposes into MOVILBA-633 (ADAS criterion check done: 0 contrary rows on snapshot 8) and MOVILBA-634 (MDVR conflict: 403 source rows explicitly say NO with nonzero equipment/id, waiting for Eugenia). No independent Elazar rule can resolve the SSOT contradiction; hold row 32 pending Eugenia via 634. Datos also retains 25 ADAS=SI/id=0 and 2 MDVR=SI/id=0 rows; the current evidence does not define what zero means there.
• coder03-mba-l-cc assigned · 1w ago
  researcher-mba-l-cc / solo
• researcher-mba-l-cc note · 1w ago
  2026-10-08T12:34:26-03:00 researcher-mba-l-cc Condensed from the children's own measurements (633, 634), not re-measured here. What the book shows today: ADAS criterion holds clean - 0 contrary rows on snapshot 8 (633). MDVR criterion conflicts with its own data - 403 source rows explicitly say MDVR=NO while carrying a nonzero equipment/id value (634), waiting on Eugenia. Separately, both fields retain id=0 rows under SI (25 ADAS, 2 MDVR) whose meaning ("yes, unidentified" vs "no device, stale SI flag") is undefined by current evidence. Short question for Elazar, ready as asked: (1) for the 403 MDVR rows - does a nonzero equipment/id override the book's explicit NO (treat as SI), or does the explicit NO win and the id is noise to ignore? (2) separately, for the 27 SI/id=0 rows (25 ADAS+2 MDVR) - does id=0 mean "yes, device present but unidentified" or is it a data-entry default meaning no device? Both need Eugenia's read of her own source, not an app-side rule - no independent Elazar policy can resolve a book self-contradiction.
• researcher-mba-l-cc note · 1w ago
  2026-10-08T12:34:26-03:00 researcher-mba-l-cc Condensed from the children's own measurements (633, 634), not re-measured here. What the book shows today: ADAS criterion holds clean - 0 contrary rows on snapshot 8 (633). MDVR criterion conflicts with its own data - 403 source rows explicitly say MDVR=NO while carrying a nonzero equipment/id value (634), waiting on Eugenia. Separately, both fields retain id=0 rows under SI (25 ADAS, 2 MDVR) whose meaning ("yes, unidentified" vs "no device, stale SI flag") is undefined by current evidence. Short question for Elazar, ready as asked: (1) for the 403 MDVR rows - does a nonzero equipment/id override the book's explicit NO (treat as SI), or does the explicit NO win and the id is noise to ignore? (2) separately, for the 27 SI/id=0 rows (25 ADAS+2 MDVR) - does id=0 mean "yes, device present but unidentified" or is it a data-entry default meaning no device? Both need Eugenia's read of her own source, not an app-side rule - no independent Elazar policy can resolve a book self-contradiction.
• coder03-mba-l-ca assigned · 3d ago
  coder03-mba-l-ca / coder
• coder03-mba-l-ca unblocked · 3d ago
  Reference convention and tracker protocol specify faithful import of both ADAS/MDVR flags and equipment IDs despite contradictions; ID 0 is retained as 0. Rechecking counts on the October SSOT before closing the summary row. No stakeholder answer or code change is required for this policy.
• coder03-mba-l-ca progress · 3d ago
  Current rule found in referencia-rutap-normativa-y-convenciones.xlsx Convenciones!A13:D13 and docs/reference/rutap-tracker-protocol.md: contradictory ADAS/MDVR flags and IDs are imported verbatim and reported, never reconciled by inference; no Eugenia answer blocks import. docs/reference/rutap-transform-rules.md T8 clarifies literal ID 0 is stored as 0 (blank stays NULL), so it is not evidence to flip a flag. Annex Datos is historical case evidence, not a new policy. Awaiting current 2026-10-13 book census before final tracker row update.
• coder03-mba-l-ca completed · 3d ago
  Criteria resolved by the existing RUTAP tracker protocol and Convenciones reference: import ADAS/MDVR declarations and equipment fields independently, report contradictions without inference or blocking; literal 0 remains 0, blank remains NULL. Current pinned 2026-10-13 book (5571 rows, 1603 open) has 0 ADAS=NO/blank with nonzero cameras/ID, and 406 MDVR=NO/blank with nonzero cameras/ID (5 open). Manual Alta MDVR=NO with ID is already guarded by MOVILBA-634. No new rule, code change or Eugenia answer is required for this summary item; report the 406 source contradictions without rewriting them.
• coder03-mba-l-ca verified · 3d ago
  Independent db04 read-only census on pinned SHA 81874621 confirms 5571 source rows; MDVR No/blank with nonzero cameras or ID union 406 (377 cameras, 135 ID, 106 both); ADAS equivalent 0. Counts are rows, not distinct vehicles. Existing Pending/Resueltos CSVs already carry the verified 406/0 result; no additional edit needed.