Content OS

Visual Agent

Proposed — not built. Tier 2 — one dependency

Back to the agent roster · Marketing OS


What it would do

Produces static and GIF creative from a draft or script, choosing template and theme, and checks output against brand guard rails before it ships.

Why an agent

The generation is a model call. The judgment is selection and QC — which template, which theme, and whether the result clears size, weight, aspect-ratio and safe-zone rules.

What it needs first

Three new things: an image model, an asset store, and a template library. The biggest infra lift of the six.

Roadmap source

Deliverable ① — Static — I · GIF — I · Video — E (page 5); guard rails on page 6 — see roadmap_ref_extracted.md.

Design notes and open questions

  • Never ship an asset that fails guard rails — return the failure, matching how the Creative Agent hard-blocks structural issues.
  • Rights and licensing for generated imagery of people is unresolved.
  • RBI rules on disclaimers within financial creative need encoding as guard rails, not left to the prompt.

Subagents

  • Template selector — which template fits this message
  • Theme generator — page 4's diff approaches, diff themes
  • Asset generator — static and GIF (video is end-state)
  • Guard-rail QC — size, weight, aspect ratio, safe zones; refuses to ship a failing asset
  • Disclaimer checker — RBI requirements inside financial creative, encoded as a rule rather than left to the prompt

Stub spec. Expand to the full overview.md + technical.md split (as the three built agents use) when this moves from proposed to scheduled.

Source: roadmap/marketing-os/agents/proposed/visual-agent/README.md