Approval and release authority are separate decisions
PiGO keeps human approval as an accountability boundary. Merge and release publication remain independent actions, each with its own state and evidence.
RELEASE PROMOTION
A release is a verified state transition, not the last sentence in a run.
Reviewer approved means code review passed. PiGO still requires a Human Gate before merge, release creation, and explicit staging or production results from an external executor.
Targets and callbacks are configured explicitly
Production URLs, deployment hooks, callback origins, and credentials enter through private deployment configuration. Environment secrets do not belong in the repository.
Promotion verifies the same deliverable
The executor contract requires staging and production to reference the same canonical repository, commit, and Docker image digest, avoiding drift from a second build.
IMPLEMENTED, NOT IMPLIED
Release path
- Reviewer approval
- Human Gate
- Controlled merge
- Release request and result callback
- Same commit and image digest across environments