Practica accepts a contradictory zone: piezas + a whole-arch region on the same row (e.g. pieza 11 + mandibulaCompleto), no check client or server
Measured 2026-08-22 (Elazar Q3 analysis): terra records one clinical axis at two resolutions - 56 FDI piezas (shared piezasDentarias, terra scope 52) and 6 arch zones (lookupOptions regionesAnatomicas) - into two sink tables. practica-form.tsx:187 and createPractica enforce at-least-one but NOT consistency: a pieza in the maxilar plus mandibulaCompleto, or a pieza plus the arch that already contains it, is accepted. Fix candidates: (a) server-side rule in practica-actions - refuse pieza+whole-arch combos and pieza-inside-selected-region redundancy, mirrored as a pre-submit toast; (b) DB CHECK is not expressible across two tables - a trigger would be db-terra-cc lane. Needs Elazar/pm ruling on whether a pieza+region mix is ever clinically meaningful before building; Q3 answer was analyze-and-tell, no build ruling yet.
Activity
-
RULED allow, not refuse (Elazar 2026-08-22: decide it yourself; coder-venus/mars/pluto no objection). Both fields record where the work was done at two granularities - piezas = sites, region = extent of the surgical field - so pieza 36 + mandibulaCompleta is a correct record of an implant inside a full-arch rehab, and pieza 11 + mandibulaCompleta is a bimaxillary practica, not a contradiction. The WI premise that the two are one axis at two resolutions was wrong: the whole-arch values are the EDENTULOUS case, which has no piezas, which is why region is an independent field and not derivable. Fix shipped as labelling + help text in practica-form.tsx and the detail page; no check client or server, on purpose. Holds while complicaciones carry no site column - revisit if one lands. Ruling recorded pm/05-client-info.md.