Marketing Review And Repair

Summary

Marketing review is where generated or run-level artifacts become operator decisions. Draft letters, mailing labels, rendered assets, and action/delivery blockers need visible state, locks, revisions, approval, rejection, publish, and repair paths.

Reader Question

How does marketing pause automation for human review and then resume or publish state without hiding the decision inside a UI component or job log?

Surface Or Workflow

Operators enter through the review queue, review detail, mailing-label review, and run detail blockers. They inspect rendered content, prompt inputs, revision history, status, validation messages, and available decisions.

Lifecycle

Rendering creates reviewable assets. Review services expose queue and detail state, enforce locks, accept revisions, record approvals or rejections, and publish approved assets. Publishing changes durable member-step, rendered asset, delivery, and run review state. Heavy provider work remains job-backed.

Repair also includes blocked action readiness, missing run tokens, distribution issues, and lifecycle quality failures. Those should appear as statuses, diagnostics, or review tasks that can be acted on.

Child Threads

  • marketing-rendering-and-assets: rendered asset state and revisions.
  • marketing-delivery-and-distribution: run-level artifacts and handoffs.
  • marketing-action-plan-dispatch: blocked or failed action execution.
  • Review Primitives

Implementation Boundaries

app/web/app/marketing/review owns review presentation and interaction. app/api/marketing/review adapts requests. services/marketing/review owns state changes and review operations. Run detail projections under services/marketing/console/run_detail keep blockers visible.

Tradeoffs

Human review slows full automation, but it prevents low-confidence or operator-sensitive output from becoming an external side effect. The cost is worth it when content, delivery, or action execution needs auditability.

Visual

The current visual is a graph neighborhood. The intended visual is a review state diagram from rendered draft to lock, revise, approve/reject, publish, delivery/action eligibility, and audit.

Source Evidence

  • app/web/app/marketing/review
  • app/api/marketing/review
  • services/marketing/review
  • services/marketing/console/run_detail
  • jobs/marketing/publish_rendered_asset/run.py
  • tests/marketing