Promotion gate philosophy
The promotion gate is a database-backed state boundary on the frame entity (the canonical reviewed item — distinct from frame_submissions, which is the ingest record). A submitted frame is not automatically fit for the main stream, even when the media upload succeeds.
This page describes the gates a frame moves through after it exists. For the upstream lifecycle of a submission as it ingresses and is processed, see Promotion workflow.
V1 gates
Section titled “V1 gates”These match the frame_status enum in Supabase SQL plan.
| Gate | Purpose |
|---|---|
team_visible | Plan.ai team members can review the frame in the Workbench. This is the entry gate — a frame row only exists once a submission reaches review. |
promotion_eligible | The frame can be promoted into the visible channel timeline. |
promoted | The frame is part of the selected channel/date stream. |
rejected | The frame stays recorded but is not eligible for display. |
Submissions that have not yet reached team_visible are pre-gate: their state lives on frame_submissions.status, not on a frame row. See Promotion workflow for that axis.
Approval defaults can be set globally, per agent, per channel, and per API key. The most specific policy wins — see Approval policy for precedence.
Human control
Section titled “Human control”V1 is internal, but it is not automatic. Agents submit. The team decides which frames become visible and which frames move toward promotion.