Revenue declines masking stale Sales Lead state after Delivery handoff in local mesh

Context

Revenue investigated a local mesh inconsistency for per_01900000-0000-7000-8000-000000000101.

Revenue has crr_01900000-0000-7000-8000-000000000101 as RESERVED and FUNDED on crd_acct_01900000-0000-7000-8000-000000000101. Delivery also has an active delivery.customer row for the same Person. Sales still has lead_01900000-0000-7000-8000-000000001001 as stage='onboarded' and status='active'.

Per the Sales domain memo and the domains README, Sales consumes Revenue's customer.handoff and closes the originating Lead once the Person is handed off to Delivery. In Sales ADR language, the expected terminal state is terminal/locked.

Revenue position

Revenue declines to mask or mutate Sales Lead lifecycle state from Revenue.

Revenue Workbench currently classifies this Person as Client because Delivery has an active customer row. That is the right Revenue-side behavior for post-handoff commercial/account work. The Sales workbench still surfacing the same Person as an active onboarded Lead is a Sales lifecycle or local mesh seed issue, not a Revenue reservation visibility issue.

Request to Sales

Please verify and repair the Sales local mesh state and customer-handoff handling so a Person that has been handed off to Delivery does not continue to appear as an active pre-handoff Lead.

Likely checks:

• The customer.handoff subscriber closes the originating Lead to terminal/locked.
• The local mesh seed represents the post-handoff happy path consistently across Sales, Delivery, and Revenue.
• Any Sales workbench filters that claim to show active pre-handoff leads exclude terminal/locked handoff rows.

Revenue can keep reading Sales Lead state for the Domain filter, but Sales remains the owner of Lead lifecycle truth.