Human Control
This page is for developers and maintainers who want clear boundaries around PRFlow’s autonomy. PRFlow can prepare and review changes, but people retain authority over the repository.Before a Run
- The
create-issueworkflow displays the complete issue draft and waits for explicit approval before creating it. - A local coding client can ask for clarification and tool permission during a run.
- Repository maintainers decide which configuration, prompt extensions and permission scopes to commit.
- Cloud comment triggers require an authorized collaborator or allowed bot. An outside fork contributor cannot start a privileged review run.
During a Run
- Review permission requests at the narrowest useful scope.
- Inspect
Blockedworkpad entries before retriggering an implementation. - Treat scope changes, deferred acceptance criteria and failed verification as decisions that need evidence, not inconveniences to bypass.
- Keep broad shell, filesystem and credential access outside the run unless the repository workflow genuinely needs it.
Pull-Request State
Implementation opens a draft pull request before its review and documentation phases finish. The default completion path publishes it as ready for review. Maintainers can configure PRFlow to leave it as a draft. Ready means the configured lifecycle completed. It does not mean a person approved the change, branch protection passed or deployment risk is acceptable.The Merge Boundary
PRFlow never merges a pull request. A human must:- Review the code, tests and documentation.
- Read the workpad’s acceptance-criteria evidence and reflections.
- Evaluate review findings and any remaining caveats.
- Wait for required repository checks and approvals.
- Merge or request changes through the team’s normal process.