KB-7009

Macro-5 Bad-Input Later-Test Expected Rejections — R2-B2 (2026-06-19)

3 min read Revision 1
laws-newR2-B2macro-5bad-input-later-testexpected-rejectionsfail-closednon-authorizing2026-06-19

Macro-5 Bad-Input Later-Test Expected Rejections — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 74 of 110) · Editorial revision: rev1 Class: bad-input later-test expected rejections · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO test run · 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 expected fail-closed rejection per bad-input class. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

State the expected (not observed) rejection a future test would assert per class.

2. Sources / evidence read

Macro-4 bad-input expected reject behavior (D51); error model (19); B2 error contract refinement (35). Main process, no reader-agents.

3. Accepted baseline (carried)

Each class resolves to no candidate stamp + a structured reason + an evidence append; never a fabricated pass.

4. Evidence / analysis — expected rejections

Class Expected behavior (fail-closed)
BI-1/2 no candidate PEN; failure appended
BI-3 skipped (out of scope)
BI-4 marked ambiguous; Owner-gated; never certify
BI-5 SOURCE_RECOVERY_REQUIRED; no stamp
BI-6/7 rejected (not B2's lane)
BI-8 rejected as fused shortcut
BI-11 rejected; row waits at its stage
BI-12 skipped (BAD_INPUT_BEHAVIOR_UNCLEAR)
BAD-14 rejected; candidate cannot reach a production field

5. Candidate / requirement / gate / result

Every expected outcome is a no-op + structured reason + evidence. These are assertions a future test would make, not results. No assertion is evaluated here (no producer exists).

6. Owner-gated future work

Evaluating these assertions against a built producer is Owner-gated; forbidden now.

7. What remains unresolved

BI-4 / BI-12 remain BAD_INPUT_BEHAVIOR_UNCLEAR.

8. Ready for GPT/Codex review

Yes — Codex should confirm every expectation is fail-closed and none is evaluated.

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/macro5-bad-input-later-test-expected-rejections-2026-06-19.md