11 - Cross-Layer Boundary Self-Review

Re-running Codex recheck CHECK_J (cross-layer boundary). Codex accepted the boundaries with a document-consistency fix only (the stale "operator permit", now resolved - doc 09).

Boundaries remain blocked / out of scope (unchanged by this patch)

concern	status	note
Stage 2.6B (permit/run/keyset/resume + authority revoke)	BLOCKED_UNTIL_AUTHORITY	separate program; not authorized by FIX7
qt001_backfill_permit / admission permit	BLOCKED	never opened in a blueprint/planning phase; never granted by operator_authorization
REAL_RUN	BLOCKED_UNTIL_AUTHORITY	real scale/capability execution; separate gate
QT001 apply (fn_dot_birth_qt001_apply/sp_dot_birth_qt001_apply)	BLOCKED since NOT_SAFE	under FIX7 both are sealed STUB_FAIL_CLOSED members; never unlocked by operator_authorization
registry-pivot repoint (system-of-record cutover)	BLOCKED_UNTIL_AUTHORITY	gated on birth/governance/registry-truth; FIX7 repoint is the QT001 control-plane writer only
governance reconciliation / Đ43 / QT-006 / raw-birth managed-object truth	BLOCKED/OUT-OF-SCOPE	adjacent cross-layer tasks, not this refactor
manifest activation / repoint / owner-ACL cutover	OPERATOR_GATED	PKG-E stages, PKG-F activates+repoints+neutralizes, PKG-G remaining cutover - all operator-gated, fresh Codex re-audit before PKG-F/PKG-G

Did the owner-semantics patch change any boundary?

No. The patch reorders S14-S16 and binds artifacts to approved surfaces; it opens no new live authority. Specifically:

• operator_authorization still grants package execution only (evidence_registry-bound, G-NO-QT001-PERMIT-DURING-FIX7) - it opens no apply/admission/REAL_RUN/2.6B and creates no readiness gate.
• Activation moving from PKG-E into PKG-F is still OPERATOR_GATED and still requires a fresh Codex re-audit (it is a governance_change, law §4G stop_without_asking_if).
• The owner transfer (S15.1) and ACL cutover (S16) are still control-object-scoped; Directus retains authority over its directus_* app tables and legitimately-owned business tables.
• The birth gateway (fn_birth_registry_auto + family) and DOT-118/119 remain DO_NOT_TOUCH.

Self-check

CHECK_J (cross-layer): PASS. Stage 2.6B, QT001 apply, qt001_backfill_permit, REAL_RUN, governance reconciliation, and registry-pivot all remain blocked/later; the document-consistency fix (operator permit → operator_authorization) is applied.