Phase 5 · Release
A gate that reads evidence, not intentions.
Promotion is decided by controls. This release carries a failing consent check, so the gate refuses it — at any hour, to anyone.
1 · Requirements → 2 · Development → 3 · QA → 4 · Release → The screen it builds → 5 · Observability → 6 · Documentation
Arrived from the QA Lab, carrying a failure.
← See the failureStory NP-AUTH-321 arrives with QA evidence: three suites green, consent-before-persistence failed. The gate reads what QA published.
AUTH-PASS-016 ✓AUTH-PASS-017 ✓PRIV-CHILD-001 ✗A11Y-BASE-001 ✓NP Release & Promotion GateDelivery workspace · Candidate build · local demo
Verified delivery session
● Signed inRole: Release managerCandidate: build 2026.8.17-rc4Target: production
1 · Request promotionCandidate enters the gate.
2 · Evaluate controlsPolicy-as-code, not opinion.
3 · RemediateFix, re-verify, re-request.
4 · PromoteCanary, watch, evidence.
Every gate is a machine check with a named owner. None can be waived from this screen.
1
Static analysis & dependenciesSAST, SCA, and secret scanning clean on the candidate — owner: Security Engineering
Pending2
Automated test evidenceUnit, integration, and acceptance suites published by QA — owner: Quality Engineering
Pending3
Child-data consent controlConsent-before-persistence must be green, and the DPIA current, for any child-data change — owner: Data Protection Officer —
PendingPRIV-CHILD-0014
AccessibilityAutomated checks green on changed journeys — owner: Design Systems
Pending5
Infrastructure policy-as-codeEncryption, region residency, and network posture verified — owner: Platform Engineering
Pending6
Artifact provenanceSigned build with an SBOM, traceable to the reviewed commit — owner: Platform Engineering
Pending·
Promotion not yet requested.
Request promotion to evaluate this candidate against the six gates.
The consent suite is failing. Under the control, a child-data change cannot reach production on that evidence — whatever the schedule, whoever asks.
GATE child-data-consent · build 2026.8.17-rc4 requires qa.consent_before_persistence = pass received qa.consent_before_persistence = fail requires dpia.status = current received dpia.status = current (reviewed 2026-07-02) ✗ PROMOTION REFUSED — child-data change on failing consent evidence gates 4–6 not evaluated: pipeline halted at first blocking control notified: DPO, story owner, release manager
Notice what did not happen. No checklist, no one paged, no judgement call under deadline. The obligation refused it by itself.
Nothing is deployed; the sequence is scripted to show the gate behaving.
5%Canary cohort
Error budgetWithin threshold
Consent ledgerWriting as expected
RollbackArmed · one step
Where the thread ends — and restarts.
See the screen it builds → Continue to Observability →Once promoted, the story becomes a screen a parent uses. Then production reports what it cost, and the loop starts again.
The point of the phase: an obligation is real only if something refuses to proceed without it. Written, inherited, proved broken, declined — one control, four phases, no meetings.
* The production workbench is internal — reachable over the corporate VPN only. This public page is a local demonstration.