Why DraPub keeps human review before publication
Understand edit confirmation, execution permissions and delivery review as decisions about a specific version and account.
Understand edit confirmation, execution permissions and delivery review as decisions about a specific version and account.
At delivery time, an editor needs to judge the version in front of them. An earlier approval in a conversation does not establish that a later title, cover and body have all been checked.
Conversations, outputs and delivery actions in DraPub have different confirmation points. Understanding them helps avoid redundant checks while recognizing changes that affect the scope of an operation.
Read the object and action on a card. Is it asking for missing information, permission to use a tool, adoption of a revision, or delivery to an external platform? Each needs a different check.
A text reply has not delivered anything externally. Adopting an AI candidate can replace stored text. A tool can affect files or services. Platform delivery adds account, media and formatting requirements. Treating these as one generic approval makes the consequences unclear.
An author may edit while AI is generating. When both a current draft and candidate are available, compare them and decide what to preserve before adopting a revision. Read important facts and attachments again before delivery.
If a title changes meaning or a cover is replaced, review of the old version cannot cover the new content. A useful decision belongs to a specific version.
Give a concrete reason when declining: a missing source, unsuitable voice or wrong account. That gives the next task more guidance than a request to improve everything.
The browser extension adds a user confirmation after receiving reviewed content. Open the platform afterward to inspect the saved draft. A planned date, an extension success result and a publicly visible post represent different states.
Automations can repeat clear tasks, while confirmation steps still follow the current request. See Human confirmation and Platform delivery.
Q: Do I need to check a new version after previously saying it was ready to publish?
**A: ** Review changes to the title, text, or media and their effects. Confirmation of an earlier draft does not cover later changes.
Q: What can automation do when human confirmation is required?
**A: ** It can trigger defined tasks, organize material, or generate results for review. When a run reaches an action requiring confirmation, that request still needs a response.
Q: How should I reject a rewrite so the next revision is useful?
**A: ** Identify the issue and what should stay, such as an unsupported figure or unsuitable tone. Provide the source evidence so the next revision can address the specific problem.