---
id: RESP-MKT
title: Marketing Responsibilities
product_area: marketing
revision: 1
status: draft
design_intent: proposed
source_sha:
  services-marketing: d071a159fe9782bb71ff246d5c67d5bbfe07fbfa
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
modules:
  - module: MOD-MKT-MKT
    owns:
      - DOM-MKT-MKT-001
      - DOM-MKT-MKT-002
      - DOM-MKT-MKT-004
      - DOM-MKT-MKT-005
    exposes:
      operations:
        - marketingHealth
        - listAudiences
        - createAudience
        - getAudience
        - updateAudience
        - archiveAudience
        - takeAudienceOwnership
        - repinAudience
        - previewAudience
        - countAudience
        - getAudienceEvaluation
        - listLists
        - createList
        - getList
        - updateList
        - archiveList
        - listListMembers
        - addListMember
        - removeListMember
        - countEveryone
        - reconcileJobs
        - mergePlanContacts
        - mergeApplyContacts
        - resolveRecipients
        - planRelationship
        - resolveRecordPeople
        - evaluateGate
        - selectAddress
        - dedupeRecipients
        - buildCountChain
        - laneCheck
        - suppressedAddressesAmong
        - submitInTransaction
      events: []
    delegates:
      - concern: 'Saved-query definitions, dataset descriptions, query authorization and person-scoped source reads'
        to: MOD-PFM-QRY
      - concern: >-
          Contact and organization records, affiliations, contact status, global opt-out and future
          subscription consent
        to: MOD-CRM-ENT
      - concern: Merge orchestration and contact aliases; invoking Marketing’s participant for its references
        to: MOD-CRM-DQ
      - concern: Invoice data and the owner’s recipient relationship declarations
        to: MOD-ACC-TRX
      - concern: >-
          Template publication, request processing, marketing-lane delivery, unsubscribe headers and
          suppression storage
        to: MOD-PFM-NOT
      - concern: Shared durable job execution and application licensing
        to: MOD-PFM-OPS
      - concern: 'Caller identity, permission assignment and application admission'
        to: MOD-PFM-SEC
      - concern: Console application shell and navigation
        to: MOD-PFM-CSH
      - concern: Workspace provisioning and cleanup through the Marketing lifecycle participant
        to: MOD-PFM-TNL
      - concern: Custom-field architecture; the current Marketing milestone authorizes no custom-field surface
        to: MOD-PFM-MTD
    guarantees:
      - INV-DOM-MKT-MKT-001-01
      - INV-DOM-MKT-MKT-001-04
      - INV-DOM-MKT-MKT-001-05
      - INV-DOM-MKT-MKT-001-07
      - INV-DOM-MKT-MKT-001-08
      - INV-DOM-MKT-MKT-001-09
      - INV-DOM-MKT-MKT-001-11
      - INV-DOM-MKT-MKT-001-12
      - INV-DOM-MKT-MKT-001-14
      - INV-DOM-MKT-MKT-002-01
      - INV-DOM-MKT-MKT-002-02
      - INV-DOM-MKT-MKT-002-04
      - INV-DOM-MKT-MKT-004-01
      - INV-DOM-MKT-MKT-004-02
      - INV-DOM-MKT-MKT-004-05
      - INV-DOM-MKT-MKT-005-01
      - INV-DOM-MKT-MKT-005-03
evidence:
  - >-
    services-marketing at d071a159: modules/marketing/**, modules/resolution/**, modules/communications/**,
    aws/marketing.service.ts, lib/record-merge/marketing-references.ts, docs/milestones/MKT-M1.md, MKT-M2.md,
    docs/forge-handoff/marketing.md.
  - >-
    react-console at baf6dae3: app/(console)/console/[tenantId]/marketing/**, components/marketing/**,
    lib/marketing/**.
---

# Marketing Responsibilities

## How the Product Area Is Divided

Marketing currently has one corpus module spanning audience and list preparation, recipient computation and its side of the communications integration. The design describes these implemented foundations. Message authoring, customer sends, consent journeys and reporting require later designs.

## Marketing Campaigns, Communications and Resolution

The marketing service owns audiences with their evaluation, audit and count-job facets, plus lists and memberships. The resolution service owns in-memory recipient computation, and the communications service owns the probe request shape and submission adapter. Together they expose staff preparation and evaluation routes, internal calculation helpers, counting and reconciliation entry points, and CRM merge participant functions. They declare no module events or Submissions form publication.

The invariant references identify their observed guarantees: guarded audience mutation, atomic success history, conditional evaluation settlement, pure recipient calculation and transactional manual membership updates. They do not promise universal eventual completion, concurrent merge count accuracy or an implemented audience sending path.

## What Is Delegated to Platform and Other Areas

Platform supplies query authorization, readable source records, template and request processing, suppressions, job infrastructure and application administration. CRM owns contacts, affiliations, consent facts and merge orchestration; Accounting owns invoice records and their relationship metadata. The lifecycle participant handles workspace cleanup. The milestone excludes custom fields, while registration-level metadata remains unverified.