Macro-4 Standard IO Contract Promote Section — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-4-STAGING-WORKBENCH-IO-CONTRACT-TD-ENTRY-GATE-2026-06-19 (Deliverable 27 of 90) · Editorial revision: rev1 Class: IO contract promote section · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.

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

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. The promotion_surface section: the explicit, Owner-gated, never-automatic promotion. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Define the promote section so the only path from draft/staging to production is an explicit Owner gate.

2. Sources / evidence read

Pilot-slice staging IO contract §6 (promotion firewall); promotion-forbidden register (18); Điều 32 lifecycle (pending→approved→applied). Main process, no reader-agents.

3. Accepted baseline (carried)

Nothing flows from staging to production automatically; a validated producer is evidence, and turning that into a production write is a distinct, separately-authorized act behind the full Owner gate.

4. Evidence / analysis — promote section shape

Element	Requirement
Explicit	promotion is a named, deliberate act, never an implicit side-effect
Owner-gated	requires Điều 32 (+ standing B2 + channel + S2)
One-directional	staging candidate → production only via the gate; production never read into staging as authority
Firewall	a draft PASS does not authorize a promote (engineering ≠ authority)
Absent here	no promotion mechanism is designed; the surface is a placeholder for a future Owner act

5. Contract / requirement / matrix / result

The promote section exists in the envelope precisely so it can be left empty/forbidden until the Owner opens it. Any automatic promotion is a firewall breach → HOLD. Status this run: NOT triggered.

6. Owner-gated future work

Designing/executing promotion is Owner-gated; forbidden now.

7. What remains unresolved

The promotion mechanism is intentionally undesigned.

8. Ready for GPT/Codex review

Yes — Codex should confirm the promote section is explicit and never automatic.