Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. I got something wrong and want to correct it before Gera acts on it: Clara CAN text that Pomona Park resident after all - I checked with the wrong tool earlier, and there is no portfolio-wide texting problem. So the question is simply how to reach Larissa K. Jones, who has now been waiting four days: should somebody just ring her, or should Clara also text her today with Gera approving the exact words first? The repair ticket is still cancelled with nobody assigned either way, which is part of what the call is for.
The full question, as raised
CORRECTING MY OWN FALSE PREMISE in b92162301, which told you no Western Slope resident can be texted. That was measured with the wrong instrument and is WRONG. I used claraNumberForProperty, which resolve-outbound-address.ts states in its own header answers a different question - 'the number a PM should DIAL, an explicit map, not an inversion'. The REAL send-path resolver, resolveOutboundAddress({propertyId:'appfolio-392'}), returns +19708220641, source 'attachment', from a live org-level line attachment on Western Slope (slot primary, provider elevenlabs, attached 2026-09-19T20:22:23Z) that the static map knows nothing about. Control in the same run: appfolio-45 resolves +18442853526 via the code map, so the probe discriminates. THREE CONSEQUENCES: (1) Clara CAN text this resident; (2) there is no portfolio-wide texting gap; (3) Fable's 'map a number' remedy is already done, in exactly the shape it prescribed - outbound pinned at the shared 970 line via the attachment mechanism. What IS broken is narrow: scripts/send-clara-sms.ts:135 reads PROPERTY_TO_PHONE_MAP directly and dies at :136, so the manual bug-recovery tool is blind to line attachments while the product path is not. That fix is in-plan and reversible, so I am assigning it myself and NOT asking you about it. Reply routing: inbound is keyed on the resident's own phone (GSI1PK=recipientPhone), so her reply is findable; residual I did not trace is which property the inbound router stamps. So the only thing left for you is the resident herself.
Why, and what was tried
The session raising this recommends: A person rings her today, and Clara texts her once Gera okays the words This is what the decider ruled twice before my bad measurement muddied it (f9feb6dce, and the advisory on the folded block): the text reaches her today even if the call misses, and only a person can learn why she rang and settle a cancelled ticket that carries no reason. Now that the send path is known to work, the text option is genuinely available rather than theoretical. The wording must make NO follow-up promise - an unbacked promise is banned by promise-backing-policy.ts after the Willows incident, and her escalation has no owner - so the staged draft is an apology plus one question: is rainwater still getting in. Nothing sends until Gera approves those words. Tried first, unsuccessfully: f9feb6dce RESOLVED (ring her back AND text her) and f72810522 ruled the lane blocked - but BOTH were briefed on my wrong 'cannot text' measurement. I am not disputing their reasoning; I am correcting the facts under it, which makes their preferred remedy executable rather than impossible. The one new act this uncovers (the recovery script's stale lookup) I am assigning myself, since it is in-plan and reversible.
2578cb67 (adopted from d656b282) is parked on this.