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.
13 questions on this
In plain terms. Which does Gera pick on each of three calls? They are about the new nothing-falls-through rule for Clara's conversations: whether the rule goes on the page, what the whole system is called, and whether a 2 AM hand-off emails at once or waits for morning.
0 of 3 answered
1Section 7a 'Nothing falls through' after Figure 6 plus row 13 in section 12, Trinity's draft in bridge thread catch-all-and-system-name-2026-10-14, with the four fixes from her audit (7a-audit-final, same thread): reuse the engine's existing outcome list; 'error' and 'door down' alert engineering only; recipients via the engine's one resolver from the door the message arrived on; one shared outcome step every path calls. Western Slope's engine is already on with a company inbox (prod read 10-14).
In plain terms. Should the "nothing falls through" rule go on the PMS-conversations page? On Oct 13 a business tenant at Western Slope called twice about a leak; Clara could not find the address, took no message, and nobody at the company was told. Trinity's rule: every message ends in one of four recorded results (Clara handled it, saved only, the team's turn, or handed to the team with a reason). No result means it is handed to the team automatically, one email per person, to the company's team inbox. Trinity audited the draft: it fits, with four small fixes folded in.
Why the raiser recommends it
The session raising this recommends: Put the rule on the page, with Trinity's four fixes One rule at the front door replaces four hand-wired checks; the Oct 13 calls replay into a recorded hand-off.
2Name for the PMS-conversations system. Trinity's note: not 'Clara' (product persona; plumbing bugs would read as 'Clara did X', and anything outside it reads as 'not Clara'). Sub-names under Reception: front door, the desk (identity), the person's file (one conversation), whose turn (engage), doors (outbound), 'While you were out' (catch-all; the exact phrase is kept out of the button because the lint forbids the word you). Under Spine: Loose ends. Under Switchboard: No line left ringing.
In plain terms. What should the whole system be called? Gera asked for one name covering the front door, who the person is, their one conversation, whether Clara or the team answers, the ways messages leave, and the new catch-all. Trinity proposed three and recommends the first; Gera's own earlier ideas are listed too.
Why the raiser recommends it
The session raising this recommends: Reception, catch-all is the note left for staff It is what a property office actually has, matches the AI-employee pitch, and the catch-all name says exactly what it does.
3Trinity's section 12 row 13 option (a) vs (c): notice emails at once day or night, or a morning digest for non-emergency hand-offs. Fede 10-13 standup: 'just email their general email ... an extension of the existing notification engine'.
In plain terms. When Clara hands something to the team at 2 AM, should the email go right away or wait for morning? Fede said on Oct 13 to just email the company's general inbox.
Why the raiser recommends it
The session raising this recommends: Email the team inbox right away, day or night Fede already said email the general inbox; an email at 2 AM wakes nobody and is there when the office opens.
Why, and what was tried
Tried first, unsuccessfully: Smith audited the Oct 13 Western Slope calls and the voice backstops; Trinity drafted the page text, the section-12 row and three names; Smith read prod and found Western Slope's team-notify engine already on with a company inbox, which removed the turn-it-on question. The remaining calls are Gera's: doc approval, the name, and overnight timing.