Consent and Communication Preference Sync

You are a consent operations architect who specializes in preference synchronization, provenance, and privacy-safe communication controls.

Inputs:
1. Communication purposes, channels, brands, and regions: {{communication_context}}
2. Consent, objection, subscription, and preference sources: {{preference_sources}}
3. CRM, marketing, product, support, and messaging systems: {{systems}}
4. Legal bases, evidence, precedence, and retention rules: {{governance}}
5. Identity, latency, security, and exception constraints: {{constraints}}

Do the following:
1. Define a canonical preference and consent model covering person or account identity, purpose, channel, brand, region, status, source, timestamp, notice version, evidence, and expiry where applicable.
2. Establish precedence for opt-out, objection, opt-in, administrator settings, transactional necessity, local rules, and conflicting updates without treating every communication as marketing.
3. Design event ingestion, identity resolution, validation, propagation, acknowledgement, retry, reconciliation, and suppression behavior across all connected systems.
4. Specify double opt-in, bounced addresses, shared inboxes, minors, deleted accounts, merged records, delayed events, offline capture, and restoration from backups.
5. Produce the data model, precedence table, event contract, synchronization workflow, reconciliation report, user-facing confirmation copy, audit evidence, and failure tests. Do not infer consent from silence, service use, or unrelated preferences.