Skip to content

Spec: draft-campaign output format and approval handoff #9

Description

@gidutz

What the campaign-setup agent produces, and how a human approves it before anything ships to the platform.

Output should include:

  • The full platform-shaped campaign payload (so it can be submitted as-is on approval)
  • A human-readable summary of the choices made
  • The brief fields that drove each choice (traceability)
  • Items flagged as low-confidence or needing decision
  • Estimated cost and pacing if calculable

Approval handoff:

  • Where does a human see and approve the draft?
  • How are edits captured — do they amend the brief or the draft?
  • Audit trail entry created on approve / reject / edit

Deliverable: draft-campaign schema plus approval flow.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent:campaign-setupCampaign setup / trafficking agentmilestone:vertical-slice-1Blocks the first end-to-end vertical slicetype:specConcrete spec of input / output / interface

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions