Growth accepts Platform's person.updated archive propagation ask and commits the Growth consumer that suppresses archived Persons from acquisition eligibility while preserving historical attribution
Why
Platform's archive propagation memo closes the producer-side gap Growth needs for test-data cleanup and do-not-contact semantics. The shape is right: Platform owns Person status, person.updated carries the canonical post-update Person plus changed_fields, and consumer domains apply their own active-surface suppression without deleting historical domain records.
Growth accepts the ask. This is the right path for taking archived or test-mode Persons out of current acquisition surfaces. It is not a request to delete Growth's form_submission rows, attribution rows, or warehouse growth.touchpoint history. Those records remain the audit trail for how the Person first entered the funnel.
What
Growth will add a person.updated consumer in the Growth repo and filter exactly on Platform's recommended predicate:
changed_fields.includes("status") && person.status === "archived"
On that predicate, Growth applies archive semantics to acquisition eligibility for the referenced person_id. The first implementation target is suppression from active Growth-owned acquisition messaging and retargeting eligibility. Where a new touch later stitches to an archived Person, Growth treats the touch as attributed-but-archived: visible for history and diagnostics, excluded from current acquisition reporting and campaign-actionable segments.
This keeps the domain split intact. Platform owns the Person status transition and event emission. Growth owns acquisition eligibility, attribution, and funnel reporting treatment. Sales owns Lead lifecycle handling and files its own sibling reply for cadence or Lead-state behavior.
The historical side is intentionally preserved. Existing form_submission rows, lead_attribution rows, subscriber-promotion history, and growth.touchpoint rows remain available for audit and longitudinal analytics. Archiving a Person stops current acquisition action; it does not rewrite the past.
Asks
None. Growth's reply obligation on the Platform thread is satisfied by this memo and the frontmatter commitment above.
Growth will read Sales' sibling reply for Lead lifecycle semantics, but Growth is not waiting on Sales to build the Growth consumer. The two consumers are independent and can land in either order, as Platform's memo describes.
References
- Platform parent memo:
memos/2026/2026-05-11-platform-archive-propagation-sales-growth.md - Identity contract:
contracts/identity/README.md - Canonical fields spec:
contracts/identity/person-canonical-fields.md - Person resolution semantics:
contracts/identity/person-resolution-semantics.md - Event envelope contract:
contracts/event-envelope/README.md person.updatedpayload schema:contracts/identity/schema/payloads/person.updated-v1.json- Event-types registry:
contracts/event-types-registry.json - Growth domain doc:
domains/growth.md