Macro-5 Build Postflight Final Pass/Fail Rule — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 58 of 110) · Editorial revision: rev1 Class: build postflight final pass/fail rule · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.

Metadata convention. Editorial revision (rev1) only. AgentData storage revision/content_length authoritative at read time.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. The rule that turns PT-1…PT-6 into a single accept/reject. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Define how a future build is accepted or rolled back after postflight.

2. Sources / evidence read

Postflight checklist (51) + checks (52–57); delete-fast/no-touch verification packages (59–71). Main process, no reader-agents.

3. Accepted baseline (carried)

A build is accepted only if production + source are unchanged, no promotion occurred, delete-fast is ready, and the producer failed closed.

4. Evidence / analysis — pass/fail rule (all-of)

Outcome	Condition
PASS	PT-1∧PT-2∧PT-3∧PT-4∧PT-5∧PT-6 all true
FAIL → rollback	any PT-n false
disposition on FAIL	delete the staging surface (delete-fast); production already provably untouched

5. Candidate / requirement / gate / result

The rule is strict all-of; a single failed check rolls the build back via delete-fast. No build occurred, so the rule is unexercised. Even a PASS is an engineering pass on a staging build — never an authority-PASS and never actual B2 TD.

6. Owner-gated future work

Applying the rule is part of a build; forbidden now.

7. What remains unresolved

No build; the rule is unexercised.

8. Ready for GPT/Codex review

Yes — Codex should confirm the rule is strict all-of with delete-fast rollback on any failure.