> For the complete documentation index, see [llms.txt](https://oodlz-ai-studio.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oodlz-ai-studio.gitbook.io/docs/outbound-agents/awareness/approval-gates.md).

# Approval Gates

2 approval gates the brand controls — Gate 1 on topics before article generation, Gate 2 on articles before publish and repurpose.

> **2 explicit approval points the brand controls — autonomous in between, never autonomous through.**

The Awareness producers do the heavy lifting — research, writing, formatting, image generation, social repurposing, scheduling. They never publish without explicit approval. 2 gates sit in the pipeline at the points where editorial control matters most: topics before article generation, articles before publish and repurpose.

## How It Works

The pipeline is producer → gate → consumer. The Topics producer writes new candidates as Pending Review. The brand reviews each topic in the workspace and changes the status to Approved (or Rejected). The Articles producer only acts on Approved records, so nothing gets generated unless the brand says yes.

The same pattern repeats for Articles. The Articles producer writes draft articles as Pending Review. The brand reviews each article in the workspace — title, content, images, metadata — and changes the status to Approved. The Repurpose producer only acts on Approved records, so nothing publishes or repurposes unless the brand says yes.

Between gates, the producers run autonomously. At each gate, the brand has full editorial control without needing to touch the pipeline mechanics — the only action is updating one field in the workspace.

## What You Get

* 2 approval gates exactly where editorial control matters — not 1, not 5, not buried in 17 micro-approvals.
* Status-driven gating — the brand updates one field, the producers downstream pick it up automatically.
* Autonomy between gates — once a topic is approved, article generation runs without further intervention; once an article is approved, scheduling and repurposing run without further intervention.
* Reject paths supported — Rejected status is treated as terminal for that record, consumers skip rejected work.
* Workspace-driven, not workflow-driven — the brand never opens any backend tool to approve work.