Read-Only S8 Rollback-Surface Recheck (2026-06-18)
Read-Only S8 Rollback-Surface Recheck
Date: 2026-06-18 · Workstream: LEGO-PILOT-SLICE-0-R2-B2-READONLY-EVIDENCE-OWNER-PATH-MACRO-2026-06-18 (Deliverable 18 of 30) · Editorial revision: rev1
Class: read-only rollback-surface recheck (S8) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO rollback script · NO rollback executed · HOLD-2 OPEN · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time; not pinned here.
S8-recheck lock. Read-only re-confirmation of the S8 rollback reuse-candidate surface:
fn_iu_enactpresent (IU-lineage, reuse candidate); the B4 downstream-certify trigger live; HOLD-2 OPEN. It writes no rollback script, executes no rollback, resolves no HOLD-2.
0. Status and non-authorization
STATUS: PASS — engineering / read-only. Fresh confirmation: fn_iu_enact present; trg_birth_auto_certify live (downstream effect real); HOLD-2 unresolved. Engineering PASS ≠ authority PASS. Default disposition: HOLD. No rollback script/execute; no DB write/DDL/DML; no HOLD-2 resolution; no TD; no blocker resolved.
Evidence basis — FRESH_READONLY_EVIDENCE (FQ-14, FQ-8) + INHERITED_KB_EVIDENCE (fn_iu_enact is IU-lineage/atomic; HOLD-2). Reading discipline: main process, no reader-agents.
1. Purpose
Re-confirm read-only the S8 surface (GATE-8 read-only half): the reuse-candidate function exists, the downstream-certify trigger is live, and HOLD-2 is still open. §4 records the readback.
The one rule: B2's rollback unit = one producer run; fn_iu_enact / Đ39-snapshot are reuse candidates (patterns, not turnkey, distinct from birth-certify). Reading confirms presence; it writes no script and does not assume coverage.
2. Sources / evidence read
Deliverable 1 (FQ-14/8); Mega Gate S8 Rollback / Downstream-Certify Readiness (S8R-1…S8R-5; HOLD-2 OPEN); R2 readiness scope §8 (fn_iu_enact atomic for IU lineage, distinct from birth-certify). Read directly, main process.
3. Accepted baseline (carried)
S8 [PARTIAL]: unit = one producer run (defined); reuse candidates = Đ39 pre-batch snapshot + fn_iu_enact atomic/fail-closed/post-verify pattern (IU-lineage, distinct from birth-certify); downstream-certify interaction open; HOLD-2 OPEN (no atomic end-to-end birth-certify promote txn); no script.
4. Read-only evidence observed (FRESH, 2026-06-18)
| Check | Result | FQ |
|---|---|---|
fn_iu_enact present |
yes (in pg_proc) — the reuse candidate exists |
FQ-14 |
trg_birth_auto_certify live |
enabled (tgenabled='O') — completing all three inspect_* triggers B4's independent certify (the downstream effect S8R-4 must account for) |
FQ-8 |
fn_birth_auto_certify present |
yes | FQ-14 |
| HOLD-2 (atomic birth-certify promote txn) | unresolved — fn_iu_enact is IU-lineage, must not be assumed to cover birth-certify |
INHERITED |
Reading. The S8 reuse-candidate pattern (fn_iu_enact) is confirmed present (read-only) and remains a candidate to evaluate, not turnkey and not birth-certify coverage. The downstream-certify effect is real (B4 trigger live). HOLD-2 is OPEN: no single existing transaction cleanly brackets a stamp + the triggered certify; this run resolves nothing.
5. Classification / result (G-8)
| Element | New status |
|---|---|
| Unit defined (S8R-1) | carried (design) |
fn_iu_enact / Đ39-snapshot reuse candidate present (S8R-2/3) |
PARTIAL_READONLY_VERIFIED (FQ-14: present; still candidate-not-turnkey) |
| Downstream-certify interaction (S8R-4) | open; mechanism FUTURE_TD (FQ-8: trigger live) |
| HOLD-2 | OPEN (write-gated workstream) |
G-8 verdict: reuse-candidate + downstream-effect read-only confirmed; mechanism + HOLD-2 write-gated/open. No script written; no rollback executed; HOLD-2 not resolved.
6. Owner-gated future work
| Future work | Gate required | Forbidden now? |
|---|---|---|
| Define/execute the per-run rollback mechanism (incl. downstream-certify unwind) | Điều 32 + S8 within B2's package | Yes |
| Resolve HOLD-2 (build an atomic birth-certify promote txn) | separate Owner-gated workstream | Yes |
Evaluate fn_iu_enact / Đ39-snapshot for reuse |
Điều 32 (design) — pattern not turnkey | Yes |
7. What remains unresolved
- HOLD-2 OPEN — no atomic birth-certify promote transaction;
fn_iu_enactis IU-lineage only. - Downstream-certify unwind is FUTURE_TD.
- Blockers — all OPEN.
8. Ready for GPT/Codex review
Yes — as a read-only S8 surface recheck.
Core rule: fn_iu_enact present (reuse candidate, IU-lineage, not turnkey); B4 downstream-certify trigger live; HOLD-2 OPEN; no script written, no rollback executed, HOLD-2 not resolved.
Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.