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. One renter record at a Situs property now holds two people from the same household: one person's name, plus the other person's email, phone and two rental applications. Should we split it into two records, or leave it as one shared household record?
The full question, as raised
pers_f0dbeea1 (org Situs, property-51) blends two humans: PROFILE from guest card 8990 (2026-10-21), plus a second email+phone+rentalApp 2498 attached 2026-10-22 00:01Z via the different-contact restamp path, and now rentalApp 2516 adopted 2026-10-30 04:46:19Z by resolveKnownRowMatch right after the email rung refused it (email-contact-conflict, names disagree). Split the second human's claims (email, phone, rentalApp 2498/2516) onto a fresh Person, or keep the blend?
Why, and what was tried
The session raising this recommends: Split into two records The name check says these are two different people; one record means texts and calls from either one land on the other's thread. Tried first, unsuccessfully: Read propflow-prod claims and the prod sync log: the refusal fired, then the last matching step glued the application anyway because the record already holds both people's contacts. Amended the design doc (PR 23663); no data write, since a split is a prod-data change.