Authority Receipt
Approvedrodchalski approved this action.
Human review was required because some changed content could not be analyzed.
View approval and policy details
Incomplete analysis
hold.incomplete_analysis · outcome-router-v1
Files in the recorded assessment
- action.yml
- test/run-tests.sh
This records the checks used for this decision, not a guarantee that the change has no risk.
Policy at signing: main · 53ccb94501663b05533fdbedca1994adac5afdae
permission-protocol/deploy-gate · Related PR #70
Deploy gate authorization approved
Signed action and target
- Recorded decision maker
- rodchalski · Approved
- Recorded capability
- deploy:main
- Environment
- production
- Repository
- permission-protocol/deploy-gate
- Recorded at
This legacy capability identifier is also used for pull request approvals. It does not distinguish merge approval from deployment approval or prove either action occurred.
Signature verified by the service
Permission Protocol signed this receipt to record rodchalski’s decision.
Pull request merged
GitHub reported the related pull request merged after this approval. The authorization window has since ended, so this receipt cannot authorize anything further.
Merge reported by GitHub:
Authorization expires:
Service record checked: Oct 18, 2026, 7:54 AM UTC
Policy and approval evidence
The issuer signs the receipt. Its recorded decision maker and authentication method describe who made the decision; they are not a separate receipt-signing key.
Policy rules are checked again before unused authorization can be used. Later changes do not rewrite a completed authorization’s signed history.
The policy rule records how PP evaluated the change. A rule that requires review can be followed by a human approval or rejection. The signed decision recorded here is approved.
Related request context
PR and file details provide context. They are not part of the signed deployment scope.
Target branch (related PR)
mainTechnical verification
The signature check authenticates the receipt against the issuer key. It does not prove that a pull request merged, a deployment ran, or an action is still authorized now.
Recheck the signed artifact locally. This page and its key set come from the service; use the command and a separately trusted key for an independent check.
Verify it yourself
Open this page in your browser to show its verification command.