---
title: Preflight, controlled release and fresh acceptance
shelf: Playbooks
url: https://library.feedthejoe.com/playbooks/08-release-and-independent-acceptance/
markdown: https://library.feedthejoe.com/playbooks/08-release-and-independent-acceptance.md
author: Joseph W. Anady
publisher: THATDEVELOPERGUY LLC
status: "Expansion: Source linked operating design"
summary: An actual owner authorized change has a defined build/environment and predeclared acceptance contract. The library itself performs no deployment.
published: 2026-09-09
modified: 2026-10-14
release: 2026.09.12-g40
words: 336
sources:
  - discipline:D44
  - discipline:D45
  - discipline:D46
cites:
  - https://library.feedthejoe.com/disciplines/r21-qa-sdet/
  - https://library.feedthejoe.com/disciplines/r25-release-change-management/
  - https://library.feedthejoe.com/disciplines/r26-independent-acceptance/
  - https://library.feedthejoe.com/operating-model/discipline-source-register/
  - https://library.feedthejoe.com/disciplines/r01-site-reliability/
  - https://library.feedthejoe.com/disciplines/r20-application-security-privacy/
  - https://library.feedthejoe.com/disciplines/r22-adversarial-red-team/
  - https://library.feedthejoe.com/disciplines/r24-solutions-architecture/
rights: © 2026 THATDEVELOPERGUY LLC. All rights reserved.
---

# Preflight, controlled release and fresh acceptance

**Lead:** R25. **Consulted roles:** R01, R20, R21, R22, R24, R25, R26 plus affected domain owners. **Mode:** read only diagnosis until actual authorization.

## Entry condition

An actual owner authorized change has a defined build/environment and predeclared acceptance contract. The library itself performs no deployment.

## Sequence and ownership

### 1\. Freeze the contract

Record project/build/environment, exact change scope, required checks, allowed exceptions and required independence. Preserve the contract hash before collecting acceptance records.

### 2\. Verify readiness

R01 demonstrates recovery readiness, R21 runs preflight regressions, R22 challenges approved assumptions and R20 reviews critical exposure. R24 resolves conflicts.

### 3\. Authorize execution

R25 confirms the actual operator, sequence, stop thresholds and rollback owner. A JSON pass or role prompt cannot grant permission.

### 4\. Observe the deployed result

Collect timestamped raw evidence for the actual build. R26 executes fresh required journeys, discloses reviewer relationship and does not accept builder summaries on trust.

### 5\. Record the bounded verdict

Validate the record structure and artifact hashes with the offline gate, then have the responsible owner inspect truth and independence. Report failed/blocked requirements, residual risk and actual rollback if performed.

## Evidence package

Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag.

## Acceptance

* Required checks have fresh scoped evidence and match the declared build
* Independence satisfies the agreed policy and is truthfully disclosed
* A responsible owner, not the tool, makes the release decision

## Stop or block

Never create a fake second reviewer identity or modify a failed requirement after testing to obtain a pass. The offline evidence gate checks consistency, not truth or authority.

## Role and source references

* [R21 · QA/SDET Engineer](https://library.feedthejoe.com/disciplines/r21-qa-sdet/)
* [R25 · Release/Change Manager](https://library.feedthejoe.com/disciplines/r25-release-change-management/)
* [R26 · Independent Acceptance Engineer](https://library.feedthejoe.com/disciplines/r26-independent-acceptance/)

Primary source IDs: D44, D45, D46. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause.