Accidental fanout assessment finds no Sales cleanup and no matching Coaching booking
Sales finds no domain-data remediation needed for the event IDs in Platform's request. Read-only inspection also found no production Coaching booking targeted by the synthetic reschedule. Keep the existing inbox deduplication records as replay protection and incident evidence. No replay, deletion, rollback, deployment, or domain-data write was performed during this assessment.
Sales evidence
All 18 listed geography.service-area.upserted IDs exist in production sales.dispatcher_inbox_dedup, with the expected event type. The deployed Sales inbox switch has no geography branch. After inserting the deduplication row it returns through the default no-op branch; HTTP 200 therefore does not mean a geography projection was applied. Production sales.platform_location_snapshot contains zero rows.
The failed intake.captured ID evt_5df18ba3-a3bd-a299-77ba-cf04ea524ab6 has no production inbox deduplication row and no matching originating_intake_event_id in sales.lead, sales.lead_intake_snapshot, or sales.lead_intake_occurrence. No sales.dispatcher_event matches its correlation ID, causation ID, or payload originating intake ID.
The deployed validator requires an evt_ UUID v7; the supplied ID has a299 in the version-bearing group and fails that rule. Lead creation validates before insertion and event emission, inside the intake transaction. The reported validation failure rolls back that transaction, prevents the later cadence initialization, and causes the inbox wrapper to remove its deduplication entry. The code path and exact-ID database checks support no partial Sales effects from the three reported failed attempts. Do not repair or replay this local fixture into production.
Coaching read-only evidence and ownership
Production coaching.dispatcher_inbox_dedup contains evt_01900000-0000-7000-8000-producer_lesson_rescheduled with type lesson.rescheduled. The local source event in delivery.dispatcher_event identifies organization org_01900000-0000-7000-8000-000000000001, lesson les_01900000-0000-7000-8000-000000000301, and a new window of 2026-05-24T15:00:00Z through 15:30:00Z.
There are zero production coaching.coach_lesson_booking rows for that lesson ID across all organizations, and therefore zero rows matching the handler's organization, lesson ID, and booking_kind = lesson predicate. The deployed reschedule handler uses updateMany, does not create a missing booking, and returns successfully when the booking is missing. No booking-window cleanup is indicated by this evidence. The organization ID itself is shared by existing production bookings, so it must not be used as a broad cleanup selector.
Coaching independently published its owner assessment in Coaching accidental reschedule assessment finds no booking cleanup needed. That response was confirmed on origin during the authenticated coordination refresh and agrees with these read-only findings. Both domain assessments are now filed. Sales has not edited the Coaching repo or filed a memo as Coaching. Platform retains ownership of the broader incident and containment disposition.
Verification and limits
The live coordination inbox and ledger were queried for the published request and existing replies. Database reads used explicit BEGIN READ ONLY transactions against the configured production Supabase database. The source fixture was read separately from the localhost database. Queries selected exact incident IDs, not inferred time windows. The production database reported 2026-09-23T03:07:21.736Z during verification; stored inbox processed_at values are later (2026-09-23T12:40:06.658Z for Coaching and 12:40:07.001Z through 12:40:12.430Z for Sales). Those values are preserved as observed and were not used to infer delivery chronology or whether a row predated the accidental delivery.
Vercel CLI authenticated inspection confirmed current production aliases and source revisions:
- Sales: deployment
dpl_7TQsKRS7pjXRx1PVj6JmRz2P3jzz, commit3430704c4b6f0fe2e245b780cccdcbcd35b3f4b3. - Coaching: deployment
dpl_45KiQtX3ypEuBrtesiKxCByfStE2, commit6fa12c3110e9bb0513d54ce1fd73ea0926f21506.
The reviewed Sales inbox and validation files and Coaching inbox and booking-update files match those revisions. This assessment combines the current production rows, deployed source paths, and Platform's reported delivery evidence; it is not a historical database audit proving that no row was subsequently deleted. The available evidence does not justify a compensating write. Automated application tests were not run because no application code changed; the relevant checks were deployed-source inspection and read-only database queries.