KB-275A

Macro-2 B2 Waivable vs Non-Waivable Gate Map — R2-B2 (2026-06-19)

5 min read Revision 1
laws-newR2-B2macro-2b2waiver-mapgate-mapnon-authorizing2026-06-19

Macro-2 B2 Waivable vs Non-Waivable Gate Map — R2-B2

Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 27 of 45) · Editorial revision: rev1 Class: B2 waiver map (entry gate) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO waiver granted · NO write performed.

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

Waiver-map lock. Records what an Owner could waive (with caveat) vs what no waiver can cross, updated with fresh evidence. It grants no waiver.


0. Status and non-authorization

STATUS: PASS — engineering / decision-support. The GATE-1…11 waivable/non-waivable map, fresh-updated. No waiver granted.

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

Evidence basis — INHERITED_KB_EVIDENCE (entry gate) + FRESH_READONLY_EVIDENCE (2026-06-19). Reading discipline: main process, no reader-agents.


1. Purpose

State precisely, with fresh evidence, which gates the Owner could waive (and the caveat each requires) vs the non-waivable floor — so the Owner's three decisions (channel/Đ0-G/S2) are sized correctly.


2. Sources / evidence read

The owner waiver map (GATE-1…11 + hard floor); the gate delta; the fresh RQ-ledger; Deliverable 26 (hard floor). Read directly, main process.


3. Accepted baseline (carried)

GATE-3 waivable-with-caveat; GATE-2/7/8/10 partly; GATE-4 (channel) + GATE-5 (owner) non-waivable; GATE-6/9 hard-floor-adjacent.


4. Waivable vs non-waivable gate map (fresh)

Gate Waivable? Caveat if waived Fresh note
GATE-1 contract n/a (Go)
GATE-2 B3/B4 partly (read-only-verified shape) "B3/B4 read-only re-confirmed 2026-06-19; runtime exercise owed" FRESH (RQ-1/10/11/12)
GATE-3 Đ0-G Yes, with caveat "working source; broken anchor; STAMP/GATE least-precedented; S6 owed" Deliverables 19–24
GATE-4 channel No (selection) substrate fail-closed (RQ-4/13/14/16/17)
GATE-5 S2 owner No governance_object_ownership=0 FRESH (RQ-15)
GATE-6 staging No unbuilt
GATE-7 S7 partly (writers in TD) "S7 writers a TD item; records-not-decides" RQ-9 (kg_quality_log=0)
GATE-8 S8 partly (mechanism in TD) "rollback + downstream-certify unwind TD items; HOLD-2 OPEN" fn_iu_enact present
GATE-9 bad-input No (commitment) producer MISSING
GATE-10 B7/GUC partly (transient OOB) "no warn→block before producer; transient GUC unread (CAV-5)" persisted empty FRESH (RQ-5/6)
GATE-11 CONS/CELL scoped "B2 TD must not assume canonical materialization" B2 writes no canonical (RQ-1)

Hard floor (no waiver crosses): Deliverable 26 HF-1…HF-9.

Reading. GATE-4 and GATE-5 are non-waivable and open — they are exactly the channel and owner decisions Macro-2 prepares. GATE-3 is waivable-with-caveat (the Đ0-G ballot). The read-only-verified gates need no waiver. No waiver is granted; aggregate NO-GO holds.


5. Result

Opening actual B2 TD requires the Owner to waive GATE-3 (with caveat) AND close GATE-4/5/6, with the hard floor intact. GATE-4/5 cannot be waived — they must be decided. No waiver granted. OWNER_DECISION_REQUIRED.


6. Owner-gated future work

Granting a waivable gate (with caveat) and deciding the non-waivable gates are Owner acts; forbidden now.


7. What remains unresolved

  • GATE-4/5/6 non-waivable/open; GATE-3 waivable-with-caveat unused.
  • Blockers — all OPEN.

8. Ready for GPT/Codex review

Yes — as the B2 waiver map.

Core rule: GATE-4 (channel) + GATE-5 (owner) non-waivable (the two Owner decisions); GATE-3 waivable-with-caveat; hard floor survives any waiver; no waiver granted; aggregate NO-GO.

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

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/macro2-b2-waivable-vs-nonwaivable-gate-map-2026-06-19.md