I'm parked on you

Everything I could decide myself is decided. What's left needs you. Each one carries the recommendation of the session that raised it — if you agree, pick it and press Done. A model's opinion, where there is one, appears on the card as a receipt line; cards with no receipt were never put to a model. "I'm not sure" is a real answer and becomes work for me. You don't need to open the session — pressing Done sends your answer back and it picks up.

1Should a renter's conversation be one thread per person across the whole company, or stay one thread per person per home?

In plain terms. Right now a renter who asks about three of our homes shows up as three separate conversations. Fede wants that to be one conversation per renter across the company. Do you want that?
The session raising this recommends: One thread per person per company
Fede asked for it (09-23): a renter asking about three homes should be one thread, not three. Each message can still carry its home, so the one-property filter keeps working. Both places that pick a thread (the list grouping in src/app/api/conversations/route.ts:149 and findPersonContainer in container-resolver.ts:281) must change in the same PR.
Tried first, unsuccessfully: Checked origin/main: no portfolio doc or ADR defines the conversation key. Today it is (person, home), set in the #5467 list grouping and the #5478 outbound resolver. Gera's settings resolver (#7708/#7766/#7998) does not choose threads. No open PR touches that code. Fede's side is holding until Gera picks.

010b23e7 is parked on this.

Pick an option above, then press Done.
PropFlow Docs