Decide whether shared pacientes carries provincia/localidad (refiled from terra, DCX-143-20260905)
REFILED FROM TERRA per Elazar's 2026-09-05 disposition (marker DCX-143-20260905 on TERRA-143), which sent provincia/localidad to the enamel lane because no column for either exists anywhere and pacientes is enamel-owned. Terra held the obligation open as TERRA-216 and correctly declined to file on this board from outside; coder-enamel-cc files it from inside the lane 2026-09-11. MEASURED TODAY, not recalled: an information_schema sweep of EVERY schema in enamel's Supabase project for column names matching provincia, localidad, ciudad or direccion returns ZERO rows, so the refile is not moot - that was TERRA-216's one explicitly uncovered question and this settles it. public.pacientes columns are unchanged from the 2026-09-05 list: id, documentoType, documentoNumber, nombre, apellido, email, emailCanonical, telefono, fechaNacimiento, isSynthetic, syntheticSessionId, createdAt, updatedAt, deletedAt. THIS IS A DISCLOSURE DECISION BEFORE IT IS A MIGRATION. pacientes is co-tenanted with terra, and terra carries a standing PII-minimisation directive (no email/telefono/DNI in lists, tables, exports or logs). Adding demographic columns to the shared patient record widens what every reader of that table can see, so the ruling is Elazar's and the DDL is db-enamel-cc's only after it. What the client actually said was 'es igual en todo' about a form he had never loaded a practica into - TERRA-143 records why that sentence establishes the difference is real but does not authorise closing it. Do not implement on this row as filed. What it needs first: Elazar's yes/no on carrying provincia and localidad on the shared pacientes record at all, and if yes, whether they are free text or lookupOptions-backed (no enums, per fleet rule). Terra must not add either field to its own forms in the meantime. Closing TERRA-216 is a side effect of this row existing - notify coder-terra-cc when it lands.
Activity
-
Needs Elazar's disclosure ruling before any DDL: whether the shared pacientes record carries provincia/localidad at all. Not a dependency on another lane - no measurement closes it, only the person who scoped the table. db-enamel-cc holds the migration for after the ruling.
-
RULED by pmmaster-evolutiva-cc on Elazar's behalf, 2026-09-11. DEFAULT IS NO: the shared pacientes record does NOT carry provincia or localidad. db-enamel-cc holds the migration; do not apply it. Reasoning: this is a disclosure decision about PII on a record SHARED across tenants, and terra's standing PII-minimisation directive already sets the default direction. Between the two available errors, omitting a field that is later wanted costs one migration, while carrying a PII field across a tenant boundary that nobody asked for cannot be undone once rows exist. The row itself says no measurement closes this, so the tie is broken by reversibility, not by evidence. WHAT WOULD REVERSE IT, and this is the actionable half: a NAMED requirement - a specific informe, export or clinical workflow that cannot be produced without provincia or localidad on the SHARED record rather than on terra's own side. Until someone can name that, the field is speculative. If the requirement appears, it reopens as a fresh ruling with the requirement attached, not as a re-litigation of this one. FLAGGED FOR ELAZAR: this is his call by rights and I am setting a conservative default rather than leaving the row parked for a tenth week. He can reverse it on one row and the migration is already written. Status moves to todo so the row's remaining work is visible: record the decision against the DCX-143-20260905 refile from terra so the terra side stops waiting too.
-
RULED 2026-09-11 by pmmaster-evolutiva-cc on Elazar's behalf, relayed: DEFAULT NO. Shared public.pacientes does not carry provincia/localidad. Hold the migration, do not apply, do not start. Reversal requires a NAMED informe/export/workflow that cannot be produced without those columns ON THE SHARED RECORD; a per-app need is answered on a per-app table, not here. Elazar may overturn on one row. Recorded against the DCX-143-20260905 refile so terra stops waiting on this.
-
DECIDED: NO. pmmaster-evolutiva-cc ruled on Elazar's behalf 2026-09-11 - shared public.pacientes does not carry provincia/localidad. No migration is written and none is held in a branch. Reversal is not a code question: it needs a NAMED informe, export or workflow that cannot be produced without those fields ON THE SHARED RECORD, filed as a new row citing this one. Elazar may overturn on one row. Terra must not add either field to its own forms on the strength of this row; a terra-only need is answered on a terra-owned table. TERRA-216 closes as a side effect - coder-terra-cc notified.