P3D — B3-F1a rev3 Revision Directive Report

Date: 2026-05-13

---

b3f1a_rev3_revision_status=PASS
rev2_status=BLOCKED_REVISION_REQUIRED
b3f1b_execution_allowed=false
create_function_allowed=false
create_trigger_allowed=false
pg_mutation_allowed=false
next_recommended_action=GPT_REVIEW_REV3_PROMPT_THEN_AGENT_RECOMPILE

4 fixes

#	Issue	Fix
1	SIBLING_OUT_OF_SCOPE scoped too narrow	Global: check ALL collections with physical table, not just BIRTH_REQUIRED ∩ IN_SCOPE. DEFERRED/EXEMPT with rogue sibling = still flagged.
2	COMMENT ON in executable SQL	Removed. Optional metadata artifact if desired.
3	Function resolution LIMIT 1	Strict: pronargs=0 + prorettype=trigger. 0→missing, 1→resolved, >1→BLOCK ambiguity.
4	Helper swallows errors	Removed helper EXCEPTION. Single catch at outer gate. B3-HC detects no-op risk.

Auto-scaling principle

Fix #1 is critical for auto-scaling: if a new collection is created with a rogue sibling trigger (e.g., copied from another collection), the gate must flag it regardless of its coverage status. Without global scope, new collections in DEFERRED/FUTURE_SCOPE could silently carry unauthorized birth triggers.

---

B3-F1a rev3 Directive Report | 2026-05-13