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.

1

In plain terms. Should we merge a renter's two split identity records before her move-in in 2 days? Her apartment inquiry and her signed lease used slightly different last names (McQueen vs. McQueen-Parrish), same unit, same first name — so her contact info didn't carry over to the lease.
The full question, as raised

identity_contact_match_refused, org org_a3376147 (Situs Group). tenant-spine-stamp.ts's phone-race guard refused to fold pers_7629a673 (LaiTye McQueen-Parrish, tenant_b3caea9d, unit 8153/property 41, lease 2026-10-01→2027-09-30, appfolio tenant 5716) into pers_324e769a (Laitye McQueen, ProspectInquiry guest card 8843 for the SAME unit 8153, phone +19707869574, email themcqueens_@outlook.com). tenant-spine-stamp.ts is a DELIBERATE contact-ladder opt-out (design review C-01/C-02: a shared unit phone across different households must never auto-merge), so it ran the strict name-only guard, which refused on the hyphenated-surname mismatch. Guard fired correctly per its own design; the open question is whether THIS specific pair is the same renter. Could not corroborate against AppFolio's situsgroup tenant record for id 5716 in this run (different subdomain/credentials than the jpco Reports API access I have) to check if AppFolio's own contact fields agree.

The session raising this recommends: Merge them into one record
Same unit, same property, same first-name spelling, inquiry-to-lease timeline, and a hyphenated last name is a common maiden/married-name shape — strong same-person signal, and her move-in is in 2 days with no phone/email on her tenant record today
Tried first, unsuccessfully: Reproduced the refusal from the raw Person/claim rows in propflow-prod (smith-db), read person-stamp.ts and tenant-spine-stamp.ts to confirm the guard is a deliberate, already-shipped opt-out (not a code bug or an incomplete migration of the #11841 contact-ladder decision), checked outstanding blocks for a duplicate (b90219772 is resolved but scoped to guest-card/application bridge records under the DEFAULT contact ladder, not this opted-out tenant-sync path), and tried to pull AppFolio's situsgroup Reports API for tenant 5716's on-file contact info but only have documented access to jpco.appfolio.com

d795b140 is parked on this.

Pick an option above, then press Done.
PropFlow Docs