--- id: AREA-MKT title: Marketing product_area: marketing revision: 1 status: draft product_intent: proposed source_sha: services-marketing: d071a159fe9782bb71ff246d5c67d5bbfe07fbfa react-console: baf6dae382d6f41dce976c7f848667ccc37e076f rhythm-v2-docs: 61e160782cedd17e715344bb961aec2e8d209de3 modules: - MOD-MKT-MKT owns: - Audience preparation and stewardship. - Recipient computation and explanations of evaluated reach. - Manual contact groups and their memberships. - Marketing delivery-foundation probes and integration adapters. does_not_own: - >- Platform owns saved queries, source-query authorization, identity, role assignment, licensing, durable job infrastructure and workspace lifecycle. - 'CRM owns contacts, organizations, affiliations, consent facts and contact-merge orchestration.' - Accounting owns invoice facts and their recipient relationship metadata. - 'Platform owns templates, message rendering, delivery lanes, unsubscribe headers and suppression storage.' - >- Customer message authoring, sends, recipient preference journeys and reporting await later Marketing designs. handoffs: - to: Platform Queries what: Readable business records and dataset descriptions under the evaluating person’s authority. - to: CRM what: 'Contact facts, consent facts, affiliations and membership reassignment during contact merging.' - to: Accounting what: Invoice facts and recipient relationship declarations. - to: Platform Notifications what: >- Owned template versions and transactional marketing-lane requests; workspace suppressions return as eligibility inputs. - to: Platform Security and Operations what: 'Authorized application entry, scoped identity and durable execution infrastructure.' invariants: - Marketing remains bounded by the selected workspace. - Audience authority does not broaden source-record visibility. - Marketing consumes shared facts without taking ownership of their source records. - Preparation and delivery foundations do not establish customer sending or consent journeys. provenance: documented source: - 'rhythm-v2-docs:specs/PRODUCT-AREAS.md#Module Registry' - 'rhythm-v2-docs:specs/marketing/marketing/MODULE.md' - 'rhythm-v2-docs:specs/marketing/ACTORS.md' - 'rhythm-v2-docs:specs/marketing/RESPONSIBILITIES.md' - 'rhythm-v2-docs:specs/marketing/marketing/FINDINGS.md#Open Questions' evidence: - 'rhythm-v2-docs:specs/PRODUCT-AREAS.md#Module Registry' - 'rhythm-v2-docs:specs/marketing/marketing/MODULE.md' - 'rhythm-v2-docs:specs/marketing/ACTORS.md' - 'rhythm-v2-docs:specs/marketing/RESPONSIBILITIES.md' - 'rhythm-v2-docs:specs/marketing/marketing/FINDINGS.md#Open Questions' --- # Marketing ## Purpose and Outcomes Marketing helps customer staff prepare the people they intend to reach and understand that selection before a message is sent. It gives coordinators a common place to organize reusable targeting choices, maintain deliberate contact groups and review the reach those choices produce. Reviewers inspect that preparation, while administrators hold the sensitive authority needed for exceptional contact-status choices. These responsibilities make recipient preparation understandable to people with different jobs and levels of access. The area connects business records to communication preparation without becoming the owner of those records. Staff work with contact, organization and invoice information supplied by the areas that understand those facts. Marketing brings that information together for recipient computation and explains the resulting reach within the evaluating person’s visibility. This separation supports a useful outcome: a selection can be reviewed without treating Marketing access as permission to see all customer information. The current corpus describes preparation and delivery foundations. It also gives operations staff a way to verify the communications integration and gives background processing an explicit place in the design. Customer message creation, sending, recipient preference journeys and reporting need later designs. Readers use this area to understand the responsibility boundary before opening the detailed contracts and their unresolved findings. ## Scope and Boundaries Marketing owns audience preparation, recipient computation, evaluation explanations and manual contact groups. Its communications responsibility covers its submission adapter and delivery probe. Platform owns the shared query, security, licensing, job and workspace infrastructure that these functions use. CRM supplies contact and organization facts, affiliations and consent information. It also orchestrates contact merging; Marketing participates by maintaining its own memberships. Accounting supplies invoice facts and the meaning of their recipient relationships. Platform owns template publication, rendering, delivery, unsubscribe headers and suppressions. Those handoffs preserve the authority of each source rather than creating a second source of business truth. ## How the Area Is Divided The Marketing Campaigns, Communications and Resolution module brings together staff preparation, recipient calculation and the area’s delivery integration. Open it to understand the relationships among an audience, a recipient, a manual group and the delivery foundation, or to review a detailed planning or design contract. It is the area’s single current module; its internal service boundaries describe implementation responsibilities rather than additional corpus modules. ## Area-Level Invariants Every Marketing contract stays within the selected workspace and the authority supplied by Platform. Recipient preparation preserves the evaluating person’s source-record visibility. Shared business facts and infrastructure remain with their owning areas. A delivery-foundation design does not establish a customer sending or consent journey. ## Open Ownership Questions Audience takeover authority, independent list-reading access and the effect of retirement on future sending remain product questions. The area also needs a decision about which evaluation inputs remain available to explain an earlier result. CRM continues to own consent; later Marketing sending and preference designs need to make that handoff explicit before extending the present foundations.