I'm parked on you

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. Six leads now have their conversation saved under a different person record than the lead itself, and the count went from 3 to 6 in two days. Should the step that links a conversation to a lead also move the conversation onto the lead's person, or should the nightly check stop counting cases where one side is only a placeholder?

The full question, as raised

spine-health nightly (co.propflow.spine-health-daily) red 15 nights: 1 duplicate occupancy + 6 split prospect↔conversation persons, growing 3→5→6 (10-27..10-29). Three shapes in prod (propflow-prod reads): (a) Camellia ×3 voice prospects each on its own prospect:<id> sentinel Person, all pinned to conversations bonded to ONE session-claim Person (phone-shaped value that did not normalize, created 09-23) — stub-on-stub; (b) Situs ×2 (Zillow/TurboTenant, 10-27): prospect Person has only prospect:<id> sentinel, conversation Person minted 1s later on the convo.zillow.com relay as a session claim — the relay anchor never landed on the prospect's Person; (c) appfolio-399 ×1 (10-28): prospect Person has real email+phone, its pinned voice conversation sits on a conv:<id> sentinel. The healer merge-split-prospect-persons.ts auto-merges only the email:<phone> shape, so all 6 are REVIEW. Dup occupancy tenant_2888880e: two real backfilled Western Slope Persons each holding the occupancy (crossed rows, static since 10-17). Fork: (A) unify at the pin write — when a prospect's conversationId is set and the conversation's Person is a session-only sentinel, fold the sentinel into the prospect's Person (identity-layer writer change, HIGH tier, plus a reviewed heal of the 6); (B) detector pages only when a real-claim Person is on at least one side. #21107 (10-19) already narrowed this detector once.

Fix the linking step so the conversation follows the leadthe raiser's pick Only count it when a real person is on one side I'm not sure — go find out Take it to the engineering bridge

Why, and what was tried

The session raising this recommends: Fix the linking step so the conversation follows the lead
Option B would still hide the one lead whose real thread is on a placeholder, and the count is rising, so new ones are being written every day
Tried first, unsuccessfully: Re-ran the read-only spine check against prod, read all 7 flagged records and their identity claims, matched them to the conversation stamp's dispatch rules, checked the existing healer's safety filter (all 6 fall outside it), and reviewed the prior detector fix #21107 (tombstones only; none of these are tombstones)

665ce7ae is parked on this.

Pick an option above, then press Done.