KB-381B

Read-Only Birth-Gate GUC Persisted Recheck (2026-06-18)

5 min read Revision 1
laws-newR2-B2B7birth-gategucread-only-evidencefresh-readonlydesign-onlynon-authorizing2026-06-18

Read-Only Birth-Gate GUC Persisted Recheck

Date: 2026-06-18 · Workstream: LEGO-PILOT-SLICE-0-R2-B2-READONLY-EVIDENCE-OWNER-PATH-MACRO-2026-06-18 (Deliverable 9 of 30) · Editorial revision: rev1 Class: read-only B7/GUC evidence · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NOT technical design · NO gate flip · NO write performed.

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

GUC-recheck lock. This packet records the fresh read-only re-confirmation that the persisted birth-gate GUC layer is empty (G-10 read-only half). It flips no gate, opens no B7 design (B7 is a dependency only). The transient session GUC is unreadable by the available tools and stays out-of-band.


0. Status and non-authorization

STATUS: PASS — engineering / read-only. The persisted GUC layer is re-confirmed empty this run; fn_birth_gate present → warn-mode default; transient layer OOB. Engineering PASS ≠ authority PASS. Default disposition: HOLD. No app.birth_gate_mode/app.bypass_birth_gate flip; no dot_config gate flip; no B7 design opened; no DB write/DDL/DML; no TD; no blocker resolved.

Evidence basis — FRESH_READONLY_EVIDENCE (FQ-6, FQ-11, FQ-14) + OOB (transient session GUC, CAV-5). Reading discipline: main process, no reader-agents.


1. Purpose

Re-confirm read-only that no persisted app.* birth-gate GUC exists (so the effective mode defaults to warning), and record that the transient session layer remains unreadable (G-10 / PO-7). §4 records the readback.

The one rule: B7 (GUC/gate policy) is a dependency only, not opened here (B5_B7_SCOPE_CREEP guarded). This packet reads the persisted state; it does not design a warn→block flip.


2. Sources / evidence read

Deliverable 1 (FQ ledger); R2a §9 (persisted layer empty; transient unreadable); Đ35 note (fn_birth_gate is dot_tools-metadata-scoped, warn-mode + kill-switch, NOT the canonical-birth gate). Read directly, main process.


3. Accepted baseline (carried)

R2a (INHERITED): pg_settings app.%=0 and pg_db_role_setting=0 → no persisted bypass/default → effective birth-gate mode warning (fail-open warn); bypass kill-switch not engaged by persisted config; transient session value unreadable (residual gap).


4. Read-only evidence observed (FRESH, 2026-06-18)

Check Result FQ
pg_settings WHERE name LIKE 'app.%' 0 rows FQ-6
pg_db_role_setting 0 rows FQ-11
fn_birth_gate present yes (in pg_proc) FQ-14
transient session current_setting('app.birth_gate_mode'/'app.bypass_birth_gate') unreadable (query_pg cannot read current_setting() outside its safe-param allowlist) OOB

Reading. With no server-, database-, or role-scoped persisted value, fn_birth_gate (per its carried body) defaults app.birth_gate_mode'warning' (fail-open warn) and engages bypass only on 'true'/'1'. No persisted bypass exists; the effective persisted mode is warn. The only way a different live value could exist is a transient session SET, which the available read-only tools cannot read — that residual is OOB, confirmable only out-of-band by the Owner. No overclaim is made that a transient bypass certainly does not exist.


5. Classification / result (G-10)

Half New status
Persisted GUC layer empty (warn default) PARTIAL_READONLY_VERIFIED → met (read-only) (FQ-6, FQ-11, FQ-14)
Transient session GUC NO_GO_OUT_OF_BAND (unreadable; Owner out-of-band check)

G-10 verdict: persisted half read-only verified (FRESH); transient half OOB. B7 holds warn-mode; no warn→block flip is designed (B7 not opened).


6. Owner-gated future work

Future work Gate required Forbidden now?
Confirm the transient GUC Owner out-of-band (read-only) Yes (not done here)
Design/flip warn→block (B7) separate Owner-gated B7 package Yes
Engage/disengage the bypass kill-switch Điều 32 Yes

7. What remains unresolved

  • The transient session GUC is unreadable here (OOB residual; CAV-5).
  • B7 warn→block policy is not opened (dependency only).
  • RISK-BYPASS (latent fn_auto_approve_add residue, warn-mode) OPEN.
  • Blockers — all OPEN.

8. Ready for GPT/Codex review

Yes — as a read-only persisted-GUC recheck.

Core rule: the persisted app.* GUC layer is empty (FRESH: 0/0) → warn-mode default; the transient layer is OOB; B7 not opened, no gate flipped.

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

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/readonly-birth-gate-guc-persisted-recheck-2026-06-18.md