Approve and consume lead.intake.renewed v1

Why

Repeat forms from customers with an active Intake or Qualified Lead currently lose their intent signal in Sales and leave Growth's one-form correlation pointing at the older submission. ADR-0044 proposes an append-only association event so Sales can reuse the active Lead without hiding the newest attribution.

Sales has implemented additive occurrence storage and keeps the new routing behind SALES_RENEWED_INTAKE_ENABLED. The flag will remain off until Growth's consumer is ready. Sales is not editing Growth or Platform warehouse code.

Analytics questions

1. How many repeat forms renewed an existing Lead rather than creating another Lead? Count lead.intake.renewed rows by lead_id and renewed_at.
2. Which form should receive credit for a later qualification? Use the newest event's form_submission_id as the current correlation pointer while retaining prior associations.
3. How were automatic associations made, and where should match quality be monitored? Group the event rows by matched_by and retain both originating event ids for lineage.

Requested consumer behavior

Growth, please acknowledge ADR-0044 and implement an idempotent lead.intake.renewed v1 consumer. Store one-to-many Lead-to-form association history, then switch the Lead's current correlation pointer to form_submission_id. Future qualification must credit that newest form. Earlier forms remain historical attribution.

Platform, please route this request to the platform-warehouse owner, acknowledge ADR-0044, and ingest each event as an additional intake association. Do not materialize a second Lead creation from this event. The source event should back event time and match basis rather than deriving them from current snapshots.

Both consumers should deduplicate by dispatcher event id and expose consumer lag. Please reply with the implementation and production-readiness evidence. Sales will enable the routing flag only after Growth confirms its production consumer is current. Platform-warehouse readiness does not block operator routing, but its acknowledgement is required before ADR acceptance.

Rollout monitoring

Sales will monitor counts for associated repeats, ambiguous manual-review opens, terminal reactivations, and unconfirmed matches. Growth should monitor consumer lag, current-pointer updates, and qualification events whose current form association is missing.

References

• ADR-0044
• contracts/lead-lifecycle/README.md
• contracts/lead-lifecycle/schema/payloads/lead.intake.renewed-v1.json
• contracts/event-types-registry.json
• 2026-05-02-growth-sales-lead-reactivation-confirmed