Marketing Run Render Action Model

Summary

Marketing runtime is organized around campaign runs, member steps, rendered assets, deliveries, events, and actions.

Problem

A campaign is not executed by reading a config row and sending messages in one pass. Runs need resumable state, review, delivery attempts, action dispatch, and measurement.

Principle

Materialize executable work before jobs process it, and snapshot action plans so runtime behavior remains explainable.

Platform Shape

Run-start services create or reuse CampaignRun state and member steps. Render jobs process explicit run and flow-step work. Action services snapshot, plan, and execute side effects after render or transition gates.

Source Evidence

• docs/domains/marketing.md
• services/marketing/runtime/run_start
• services/marketing/runtime/rendering
• services/marketing/runtime/actions

Related Reading

• docs/engineering/concepts/job-run-state.md
• docs/engineering/concepts/external-command-outbox.md