Macro-4 Bad-Input Test-Run-Not-Authorized Lock — 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 54 of 90) · Editorial revision: rev1 Class: test-run-not-authorized lock · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · BAD_INPUT_TEST_RUN_DRIFT guard · 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 lock that holds the bad-input oracle at design and forbids running any test. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Prevent the oracle deliverables (49–53) from being read as authorization to execute a test.

2. Sources / evidence read

Prompt §4 (no bad-input tests)/§5 (BAD_INPUT_TEST_RUN_DRIFT); bad-input/delete-fast plan §0 (plan-not-execution lock). Main process, no reader-agents.

3. Accepted baseline (carried)

Running a bad-input test would require a built producer + a built staging surface — both forbidden in this macro.

4. Evidence / analysis

The oracle (49–53) defines what would be tested, the expected fail-closed behavior, the fail-open signals, and the no-digest-pass rule. It executes no bad input, mutates nothing, and claims no runtime result. Every "expected behavior" is a design obligation, not an observed outcome (producer MISSING).

5. Contract / requirement / matrix / result — drift trigger (→ HOLD)

Drift	Token	Disposition
A bad-input test is executed	BAD_INPUT_TEST_RUN_DRIFT	HOLD
A digest/oracle result is produced	(same)	HOLD
Status this run: NOT triggered.

6. Owner-gated future work

Executing the oracle is gated behind a built producer + staging + Owner approval; forbidden now.

7. What remains unresolved

The oracle stays conceptual; no test is run.

8. Ready for GPT/Codex review

Yes — Codex should confirm no oracle deliverable runs or claims a test result.