Human Review Gate

Most builds run end-to-end and ship. But some content is high-stakes enough that you want eyes on it before it counts as "done." J77's review gate pauses builds at the end of the pipeline, gives you a chance to read, edit, or reject, then resumes.

How it works

1. Create a build. Leave the Skip human review checkbox OFF (the default). The Review-ON badge appears next to it.
2. The pipeline runs — research, draft, critique, claim ledger, merge — as usual.
3. Instead of marking the build complete, the pipeline pauses and the build moves to Reviewing status.
4. You read the deliverable, optionally edit the markdown inline, and click Approve (or Reject).
5. On approve, the build is marked complete and downstream artifacts (audio, social, blog publishing) run. On reject, the build is marked rejected and no tokens are consumed.

Auto-approval after 24 hours

If you don't act within 24 hours, the build auto-approves and ships. This prevents builds from getting stranded if you forget. The deadline is shown on the build detail page and in the email notification.

When to skip review

Toggle Skip human review on when:

• You're running a high-volume batch (e.g., 50 blog posts overnight)
• The kind is low-stakes (e.g., internal documentation)
• You're testing settings and don't want every build to pause

For press releases, audio narration that gets distributed publicly, or any externally-facing content with named individuals quoted, we recommend leaving review ON.

Reviewer feedback (different feature)

The review gate is for your approval before publishing. Public sharing is for getting feedback from external reviewers. The two work together: review-gate a build, share the deliverable publicly, collect comments, click Incorporate Feedback for a polished revision, then approve.