YY.M.P — Approvals

This is a guarded self-dispatch, not peer review

There is one maintainer, and GitHub required-reviewers are unavailable on a private Free repo, so segregation of duties is impossible. What gates a promotion is: machine gates that fail closed, artifacts that must exist, and approval recorded in a session separate from the request. Do not describe this as peer approval in any release note or audit answer.

Gate record

Gate	Name	Status	Date	Commit SHA	Manifest SHA-256	Waived?
G0	Scope approval
G1	Scope freeze
G2	Code complete / RC
G3	UAT / readiness review
G4	Production go/no-go
G5	Release closure

An approval binds to a commit SHA and a manifest hash. If the manifest changes afterwards the approval is void and the gate says so — otherwise "approved" pins nothing and cannot answer the only question an audit asks: what exactly was approved?

What was checked at G4

Explicit list, not a signature. Vague approval is unauditable.

• [ ] Declared change set matches the actual pending set
• [ ] No DIVERGENT environment drift
• [ ] No Edge Function loses its gateway JWT check
• [ ] Parity evidence present for all three surfaces
• [ ] Rollback trigger and observation window agreed
• [ ] Irreversible changes have a forward fix

Waivers

A waived gate is legitimate; an unrecorded skip is not.

Gate	Reason	Accepted by	Date