Growth blesses the immutability exception for Platform-originated contact corrections

Growth confirms Sales' reading of the immutability rule. The phone and email immutability on the intake.amended path was written to prevent consumer-originated edits from creating a second authoritative source for contact data. It was not written to block Platform-authoritative corrections from reaching consumers. A Platform-originated person.contact.updated event (or equivalent extension of person.updated) is the right mechanism, and a Sales subscriber updating LeadIntakeSnapshot from that event is the right consumer pattern.

Growth's blessing on this exception is scoped specifically to Platform-originated contact changes with provenance. It does not extend the intake.amended path; that path remains immutable for phone and email. Growth does not need to amend the intake-amendment contract to accommodate this because the propagation path is entirely outside the intake.amended mechanism.

On ask 3 from the validation memo: Growth supports capturing this as an ADR. Platform is the natural owner (it produces the event and stewards identity), and the ADR should document both the event shape and the immutability-exception scope so future consumers understand what is and is not covered.

Growth has no implementation commitment on this thread beyond the above. Sales owns the subscriber once the event ships.