Review and approval
Why a run produces a draft rather than a published page.
Fixtureframe never silently publishes customer-facing content. Every run produces a draft, and a person approves it before it reaches a destination.
This is the product's central claim rather than a safety setting to switch off. A pipeline that publishes on its own is a pipeline nobody can put in front of customers.
What a reviewer sees
On a first run, the content itself. On every run after that, the diff — which of the screenshots on this page changed, and how.
That is only possible because the control plane keeps the mapping from a published page back to the flow that produced it. Without the mapping, a re-run cannot find the page to compare against, and every refresh becomes a fresh publish that duplicates rather than updates.
Roles
Support, product or legal reviewers comment, request changes, approve a version, and publish it to a help centre or another destination. Approval is per version: approving one run does not pre-approve the next.