promptdojo_

Batch plan and calendar — creative at volume, gated before it ships — step 7 of 7

ch 49 · campaign studio7/7
Checkpoint

One last thing before we move on. Same surface as a write step — but the lesson doesn't complete until this passes.

Checkpoint: the full calendar gate, the one that runs before anything touches the scheduling tool.

Write gate(rows) returning a dict with three lists, each preserving row order:

  • "schedule" — rows with status == "approved" AND a non-empty approved_by. These may enter the scheduler.
  • "blocked" — rows with status == "approved" but NO approver. These go back for a named sign-off, not into the scheduler.
  • "rejected" — rows with status == "rejected". These stay in the file as the record of what the team said no to.

The harness prints each list and a summary. The rows are the full relaunch calendar so far — including the teaser-story that's been sitting nameless since the gate first caught it. Expected output:

SCHEDULE 09-02 email  launch-email (dana)
SCHEDULE 09-04 ads    ad-set-a (sam)
SCHEDULE 09-05 email  winback (sam)
BLOCKED  09-02 social teaser-story (no approver)
KEPT     09-03 social meme-post (rejected, stays in the file)
3 scheduled, 1 blocked, 1 rejected-and-kept

full-screen editor opens — close anytime to keep reading.

read, then continue.