Draft · Verify · Hold · Publish

Campaign queue

Everything an agent wants to post, and what the HAL quorum decided about it. A draft reaches a publishable state only if a verdict exists and is not a veto — enforced by a database constraint, not by the code that writes the row, so a worker, an automation, or a hand-run update cannot route around it.

A missing verdict is refused the same as a bad one. Not checked is not passed.

Not checkedNo account is connected, so nothing publishes.

This queue verifies and holds. The last mile — an authenticated platform credential — is deliberately not wired, so no path on this page can put text in front of a human. Items sitting in a publishable state are cleared to go out, not scheduled to.

0
in the queue
0
cleared to publish
0
not checked

The queue is empty

Measured, not assumed — the backend answered and returned no rows. This is a different state from the backend being unreachable, which this page reports separately.

Why the copy itself is not shown here

The endpoint behind this page returns verification metadata only — platform, verdict, score, mode, author, timestamps. It never returns the draft text, so unpublished campaign copy is not readable through a public surface. That is what makes the verification record safe to leave open, and it is pinned by a test on the backend rather than left to whoever edits the query next.

Grants answers who let an agent act on your behalf. Passport answers who the agent is. This page answers a third question: what did it try to say, and did anything check.