diff --git a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-named-availability-note.md b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-named-availability-note.md
index 6ac540f..a0cb78c 100644
--- a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-named-availability-note.md
+++ b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-named-availability-note.md
@@ -212,6 +212,10 @@ So the surviving frontier is narrower again:
   byte streams, but not the auxiliary fixed body or selector bytes `[+0xb8..+0xbb]`; and
   `0x0041a950`, when the restore flags demand it, only releases the current live aux collection and
   tail-jumps back into the same `0x004196c0 -> 0x00419230` import-plus-follow-on chain
+- the world-entry load branch does not add a hidden title-specific selector in between either:
+  `0x00438c70` allocates the live candidate pool through `0x004131f0` and the auxiliary/source
+  pool through `0x0041aa50`, and both constructors tail directly into the same fixed tagged-import
+  families rooted at `0x005c93fc` and `.\Data\BuildingTypes\`
 - but the still-missing owner is the earlier non-stock writer or restore-time projection seam that
   makes some live candidates reach those later consumers with nonzero `[candidate+0xba/+0xbb]`
   despite the observed all-zero BCA corpus
diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md
index 3d04ba1..2ec5279 100644
--- a/docs/rehost-queue.md
+++ b/docs/rehost-queue.md
@@ -700,6 +700,10 @@ Working rule:
     `[+0xb8..+0xbb]`, and `0x0041a950` only releases the live aux collection before re-entering
     the same `0x004196c0 -> 0x00419230` import-plus-follow-on strip when the restore flags demand
     it.
+    The outer world-entry load branch is fixed in the same way: `0x00438c70` allocates the live
+    candidate pool through `0x004131f0` and the auxiliary/source pool through `0x0041aa50`, and
+    both constructors tail directly into the same fixed tagged-import families rather than taking a
+    title-specific source-selection branch in between.
     So the honest next queue head is now one step earlier again:
     recover the non-stock writer or restore-time projection owner that makes some live candidates
     reach those later consumer strips with nonzero `[candidate+0xba/+0xbb]` despite the observed