# GitHub branch review and outcome worksheet

This is a manual template, not a command, executable request, or approval. Gated's controlled private preview covers one uniquely named branch at an exact existing commit in a selected non-critical repository. Branch updates, deletion, merges, force pushes, and deployments are outside this operation.

**Keep private:** complete this in your team's approved location. Never include tokens, passkey material, authorization headers, private source code, or customer data. Redact repository identifiers, request identifiers, people, and evidence links before external sharing.

## Exact request

- Date and environment: __________
- Pilot owner: __________
- Repository (owner/name): __________
- Proposed unique branch name: __________
- Full existing commit SHA: __________
- How and when the commit and branch availability were checked: __________
- Task reason for this operation: __________
- Repository automation or downstream effects reviewed: __________

## Decisions

- Policy result and evidence reference: __________
- Required human reviewer: __________
- Passkey approval status and evidence reference: __________
- Inputs still match the reviewed request: yes / no / unknown
- Explicit execution requested: yes / no
- Original request identifier (private record only): __________

Policy, human approval, and execution are separate. Approval alone does not create a branch. Changed inputs require a new review.

## Outcome reconciliation

- Evidence type: live provider operation / safe-mode rehearsal / unknown
- Gated request status and execution evidence: __________
- Independent GitHub readback time: __________
- Readback branch and full SHA: __________
- Comparison: matched / mismatched / absent / unknown
- Lost response or timeout observed: __________
- Owner and next investigation step: __________

After a timeout, inspect original request status and provider state before another write attempt. Do not blindly retry or create a fresh request to escape uncertainty. Supported replay of the exact Gated request is not a generic GitHub idempotency guarantee. A safe-mode rehearsal does not prove a live write.