Core concepts

Review gates and human approval

Learn which actions require approval and how accept, reject, and return differ.

DraPub treats human review as part of the state machine, not an optional step after generation.

Actions that require confirmation

  • Applying an agent proposal to an editable document.
  • Turning a master draft into a final channel version.
  • Generating or replacing outward-facing media.
  • Delivering a package to a platform draft box or publishing executor.

Three decisions

  • Accept applies the proposal and records reviewer and time.
  • Reject preserves the original and records a reason for future generation.
  • Return for changes keeps the task open and creates another proposal with concrete instructions.

Permissions and safety

Only authorized workspace members can review. Agents, CLI commands, and extensions cannot use an alternate entry point to bypass review state. A dry run may validate the path but must remain explicitly marked as unpublished.