KB-D0E4

Macro-2 Bad-Input Proof Not-Run Register — R2-B2 (2026-06-19)

4 min read Revision 1
laws-newR2-B2macro-2bad-inputoraclenot-runfail-closednon-authorizing2026-06-19

Macro-2 Bad-Input Proof Not-Run Register — R2-B2

Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 32 of 45) · Editorial revision: rev1 Class: bad-input oracle not-run register · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO harness built · NO test run · NO write performed.

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

Oracle lock. Confirms the bad-input oracle (BI-1…12 / BAD-1…15 / F-OPEN-1…10) is not run (the producer is MISSING). G-9 stays write-gated; fail-open ⇒ reject; default REJECT on uncertainty.


0. Status and non-authorization

STATUS: PASS — engineering / control. Confirms the oracle stays a requirements set (no test run, producer MISSING). It builds/runs nothing.

Engineering PASS ≠ authority PASS. Default disposition: HOLD. No harness; no test; no bad input executed; no DB write/DDL/DML; no TD; no blocker resolved; v0.1 not overwritten; v0.2 not authority.

Evidence basis — FRESH_READONLY_EVIDENCE (2026-06-19 RQ-10/11 producer absent) + INHERITED_KB_EVIDENCE (BI/BAD/F-OPEN matrices). Reading discipline: main process, no reader-agents.


1. Purpose

Answer macro question 8 (proof half) — bad-input proofs not run — and confirm G-9 stays write-gated against a fresh-confirmed MISSING producer.


2. Sources / evidence read

The 30-file bad-input oracle readiness recheck; the inspect-producer TD-prep §8 (BI-1…12); the Mega-Gate bad-input oracle requirements (BAD-1…15, F-OPEN-1…10); the fresh RQ-ledger. Read directly, main process.


3. Accepted baseline (carried)

The fail-closed test: if invalid input would still stamp / certify / canonicalize / leak / survive delete-fast / act as approval / produce a PASS, the contract is fail-open and is rejected. Producer MISSING → behavior conceptual (BAD_INPUT_BEHAVIOR_UNCLEAR, esp. BI-4/5/12, BAD-4/5/12).


4. Bad-input not-run register (FRESH 2026-06-19)

Item Performed in Macro-2? Status
Bad-input harness built No producer MISSING (RQ-10/11)
Any BI/BAD case executed No conceptual only
Runtime PASS/FAIL claimed No no runtime result
Fail-open ⇒ reject rule applied to a built producer No no producer to test
v0.2-hardening promoted as authority (BAD-10/BI-10) No tool lock held

Producer absent (FRESH): 0 inspect-named triggers (RQ-11); only fn_birth_auto_certify names inspect_* and only reads (RQ-10). There is no producer to subject to BI-1…12 → every expected behavior remains conceptual. BI-5 depends on Đ0-G recovery (Deliverable 19–24).


5. Result

The oracle stays a requirements set; G-9 = NO_GO_WRITE_GATED. No harness built, no test run, no bad input executed; fail-open ⇒ reject and default-REJECT remain the standing requirements. OWNER_DECISION_REQUIRED (a built producer + harness).


6. Owner-gated future work

Building the producer + harness and executing BI/BAD cases are Điều-32-gated (within a governed pilot); forbidden now.


7. What remains unresolved

  • Producer MISSING → BI/BAD behavior conceptual; G-9 write-gated.
  • Blockers — all OPEN.

8. Ready for GPT/Codex review

Yes — as the bad-input not-run register.

Core rule: oracle requirements stand against a FRESH-confirmed MISSING producer; no harness, no test, v0.2 not promoted; G-9 write-gated.

Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/macro2-bad-input-proof-not-run-register-2026-06-19.md