Client consultas document for Puia: own the artifact, carry the SIX open questions, keep the 14 Implementado claims true
The client status artifact for Puia has an owner and a tracking row. This is it. Rewritten 2026-08-29 because the row described an artifact that no longer exists in that form, and a WI describing a superseded artifact is worse than no WI - it tells the next session to go update a file nobody will read. CURRENT ARTIFACT: /data-venus/evolutiva/terra/pm/docs/client-communications/2026-08-29-terra-consultas-para-puia.md, with a .docx built from it by pandoc in the same directory, plus the two screenshots it embeds. It is prose in Spanish, not a spreadsheet. The 28-row xlsx at /resource/terra/pm/client-provided-docs/2026-08-24-terra-pedidos-puia.xlsx is the PREDECESSOR and its builder script lived in a dead agent's scratchpad; do not regenerate it. WHAT THE CURRENT DOCUMENT HOLDS: an accounts section, 14 numbered "Implementado" claims verified against the running app, SIX consultas each with a "Tu respuesta" slot, a seven-row self-test table with a step 0, and a list of what is open on our side. SIX QUESTIONS, NOT SEVEN, and the deletion is the interesting one. The old seventh asked Puia whether the repeated "Complicaciones intraoperatorias" heading was a document typo. It was - our own typo, in our own reference file, duplicated from the real intra heading higher up. Asking the client to adjudicate it read as though we could not tell intra from post. Fixed at source in pm/2026-08-22-client-source-espe-implantes.md (commit 9f15f35) and the question deleted rather than reworded. The live six: exact name of the third sede; whether Periimplantitis's four cirugias stand; whether Maxilo parity is exact or has exceptions; who approves a new implant brand; who may amend the shared patient antecedentes (TERRA-113); and Dr Pasart's access (TERRA-6 / TERRA-104), waiting on his Gmail. TWO ACCOUNTS, NOT THREE. This row previously said Puia has three and named sebastian.kawka@hotmail.com as a third. He has two: sebastian.puia@odontologia.uba.ar (docente + cliente) and puia.sebas@gmail.com (alumno). The three-account claim came from Puia's own words in conversation, not from a query, and I repeated it without checking. DO NOT REINTRODUCE THE HOTMAIL EXPLANATION. Elazar ruled it out of client-facing text directly: it is a pain to explain that some hotmail addresses carry a Google identity. Internally it is true and matters - the gate is provider=google plus a non-empty sub, NOT a domain allowlist - but it does not belong in front of the client. RULES THIS ARTIFACT ALREADY COST US, do not rediscover them: - RE-READ EVERY NUMBER FROM THE LIVE DB before regenerating. Never from a source spreadsheet's Estado column, which was already stale when handed over. - A LISTO CLAIM IS SCOPED TO AN ACCOUNT. Informes and the docente-controlador list are invisible from the alumno account and the nav gives no reason. Two claims were wrong for exactly this reason before delivery. - DO NOT SHIP SCREENSHOTS WITHOUT LOOKING AT THEM. One nearly went out showing four of Elazar's personal Gmail addresses, one of them a family member's. - WE WERE WRONG AND HE WAS RIGHT ABOUT THE LOGIN. He signed in successfully on 2026-08-14 07:12; his users row was not created until 08-22. The document now says so plainly. Do not restore any version that implies he did something wrong. NOT IN SCOPE: delivering the file to Puia. Elazar's call. CLOSE CONDITION: all six questions answered and routed to the WIs they unblock, or Elazar rules the document superseded.
Activity
-
coder02-terra-cc / coder
-
Reassigned from coder02-terra-ca, which left the roster while holding this row - the row was orphaned, not idle. coder-terra-ca confirmed 2026-08-29 it should come to me rather than to them, since they retain the seven blocked app rows and this is document/client-question ownership. Client doc rewritten today at /data-venus/evolutiva/terra/pm/docs/client-communications/2026-08-29-terra-consultas-para-puia.md per Elazar. All 7 questions still open; the Pasart question changed SHAPE but did not close - see TERRA-104.
-
was: The client status sheet for Puia has no owner and no tracking row, which is how it ends up stale in front of the client. This row is the owner. ARTIFACT: /resource/terra/pm/client-provided-docs/2026-08-24-terra-pedidos-puia.xlsx Sheet Pedidos: 28 rows, columns ID / Tema / Lo que pediste / Estado / Como esta hoy en la app / Pregunta para vos / TU RESPUESTA. Sorted 7 NECESITA TU RESPUESTA first, then 19 LISTO, then 2 EN CURSO. Sheet Para probar: 6 checks with a Si/No dropdown, plus a step 0 telling Puia which of his accounts to log in with. Builder script: build_xlsx.py in coder-terra-cc's scratchpad. It writes to its own directory, NOT to /resource - the copy step is separate and easy to forget, which already produced one verification against the wrong file. WHAT THIS ROW IS FOR: 1. Carry the SEVEN open questions until Puia answers them. They are the point of the artifact and they block real work: the third sede's exact name, whether Periimplantitis's 4 cirugias stand, whether "igual a Maxilo" is exact or has exceptions, who approves a student's catalogue suggestion, whether the repeated "Complicaciones intraoperatorias" heading is a document typo, whether a student may amend the shared patient's antecedentes (TERRA-113), and whether Dr. Pasart needs to log in at all (TERRA-6 / TERRA-104 cancel if no). 2. When answers arrive, route each one to the WI it unblocks and update the sheet. 3. Keep the 19 LISTO rows TRUE. They are claims we put in writing to the client. TWO RULES THIS ARTIFACT ALREADY COST US, do not rediscover them: - RE-READ EVERY NUMBER FROM THE LIVE DB before regenerating. Never from the source CR spreadsheet's Estado column, which was already stale when handed over - it listed CR-004 and CR-018 as pending after both had shipped and predates Puia's six later items entirely. A status column is a snapshot of when someone last looked. - A LISTO CLAIM IS SCOPED TO AN ACCOUNT. Puia has three: sebastian.puia@odontologia.uba.ar is client+docente, puia.sebas@gmail.com and sebastian.kawka@hotmail.com are alumno. Informes and the docente-controlador list are invisible from the latter two and the nav shows no reason. Verified live 2026-08-24 against vUserGroups. Two claims in this sheet were wrong for exactly this reason before delivery. NOT IN SCOPE: delivering the file to Puia. That is Elazar's call, not this lane's. This row owns the artifact's correctness and the questions' routing, not its transmission. CLOSE CONDITION: all seven questions answered and routed, or Elazar rules the sheet superseded.
-
Client consultas document for Puia: own the artifact, carry the SIX open questions, keep the 14 Implementado claims true
-
CLIENT ANSWERED. All six consultas came back in the document itself, not by message - Puia filled the "Tu respuesta" lines in the Google Docs copy and returned it. The returned file is at /data-venus/terra/client-communications/2026-08-31-lezama-copy-terra-consultas-para-puia.md (md5 ae4ee3ac..., 230 lines), byte-verified against the lezama original by two agents independently. It differs from my sent copy (md5 9b53401b..., 167 lines) not only by the answers but by a Google Docs round-trip: escaped hyphens, trailing double-space breaks, and the two screenshot image sources emptied. Read the returned file for wording; this event is the durable record in case that file moves. THE SIX ANSWERS, verbatim where he was terse: 1. Nombre exacto de la tercera sede -> "esta bien asi". So "Practicas Suplementarias Profesionales" IS the name and is not our abbreviation. Nothing to change; the open question closes. 2. Modulo 6 Periimplantitis, las cuatro cirugias -> "si, quedan". Cirugia regenerativa periimplantaria, Cirugia resectiva con implantoplastia, Colgajo de acceso y descontaminacion, Explantacion por periimplantitis all stay. No catalog change. 3. Paridad con Maxilo -> "es igual en todo." This is the answer that unblocks the field-by-field comparison, and it is a claim about a codebase we can read - so it converts an open question into a VERIFIABLE task rather than closing it. Do not treat "es igual en todo" as the comparison having been done. 4. Quien aprueba una marca nueva -> "Todos los docentes". Not one named person. That is a ROLE, and terra already has a docente role, so this is implementable rather than an operational agreement. 5. Quien puede modificar los antecedentes de la ficha compartida -> "cualquiera que carga una practica". The most permissive of the three options I offered. Note what this does NOT say: the per-practica antecedentes stay frozen as the clinical record - that was never in question - and this only governs the SHARED ficha that carries forward. Unblocks the write-back half. 6. Acceso del Dr. Jorge Pasart -> "te la mando por privado al chat", and he did: jorge.pasart@odontologia.uba.ar, name given as JORGE PASART, with the note "es el gmail de odontologia como la mia" - i.e. a Google Workspace address under odontologia.uba.ar, the same shape as his own working account, NOT a personal gmail.com. THE SELF-TEST TABLE CAME BACK TOO, and one row is a NO. Rows 0-5 are "si" (row 1 typed "ai", plainly the same). Row 6, Informes filters: "Si, pero no puedo seleccionar alumnos." He then raises it three more times in the WhatsApp thread unprompted, which is the strongest signal in the whole document - as docente he sees 6 practicas and cannot tell whose they are, so the number is unreadable to him. Filed separately. TWO FEATURE REQUESTS ARRIVED IN THE SAME THREAD and neither was asked for by us. Filed separately. One of them he gates go-live on in his own words: "Si logramos esto esta para arrancar." WHAT THIS WI WAS FOR IS DONE: the artifact exists, it carried the six questions, and all six came back answered. Closing. The work each answer unblocks is tracked on its own item, not here - see the linked children.
-
All six consultas came back answered in the returned document; the answers are recorded on the note event here. The artifact existed, carried the questions and did its job. Work unblocked by the answers is tracked on TERRA-104/TERRA-6 (Pasart), TERRA-113 (ficha write-back), TERRA-139 (alumno filter), TERRA-140 (team quirurgico), TERRA-141 (marca approval) and TERRA-142 (Maxilo parity), not here.