Record Stage 5 target custody preflight

docs/LEGACY-INGEST.md

@@ -99,6 +99,14 @@ Current evidence:
 
 Movement gate:
 
+2026-06-17 custody preflight: the old Stage 5 target admission is now
+historical proof context only. The admission record sets
+`admission_lifecycle=historical-proof-target`,
+`future_execution_authorized=false`, and
+`future_execution_requires_new_admission=true`. Physical relocation remains a
+separate host-aware custody gate because the MacBook mirror can rehydrate root
+paths unless policy is checked first.
+
 Move or archive only after CTO replaces the absolute live path with archive-stable evidence or a new admitted target fixture, reruns `python3 tools/validate_cto_child.py`, reruns `python3 tools/validate_cto_stage5_target_sandbox_child.py`, and records that target ownership remains outside CTO and Core. The target-local Case task residue is now declared stale, but the absolute path dependency remains open.
 
 Rejected now: raw move, hard delete, validator path rewrites for cleanup optics, Case rerun, Harness rerun, provider mutation, target source mutation, Core mutation, Seed mutation, readiness claim, release claim.

docs/STAGE5-TARGET-SANDBOX-CUSTODY-PREFLIGHT.md

@@ -0,0 +1,44 @@
+# CTO Stage 5 Target Sandbox Custody Preflight
+
+Local planning evidence only. Not Core authority. Not Runtime authority.
+
+Source: CTO-WORK-099.
+
+## Result
+
+Status: custody-preflight-complete.
+
+Original target path remains historical proof context only:
+
+```text
+/home/svrnty/workspaces/cortex-os/cto-stage5-target-sandbox
+```
+
+The target sandbox remains in place during this slice. Do not move the target sandbox in this slice.
+
+## Admission Lifecycle
+
+The Stage 5 target admission now declares:
+
+- `admission_lifecycle`: `historical-proof-target`
+- `future_execution_authorized`: `false`
+- `future_execution_requires_new_admission`: `true`
+- `root_path_dependency`: `historical-reference-only`
+
+Any future Stage 5 execution requires a new admission record, new approval
+text, current target validation, and fresh Harness evidence. The old
+2026-06-01 approval remains proof history only.
+
+## Custody Decision
+
+Physical relocation remains a separate host-aware custody gate. That gate must:
+
+- preserve the target sandbox outside the umbrella with a manifest;
+- prove the preserved target validator still passes from the preserved path;
+- prove root absence or record any MacBook sync rehydration;
+- keep target ownership outside CTO and Core;
+- avoid hard deletion.
+
+No target source mutation, Case rerun, Harness rerun, provider call, runtime
+start, browser open, branch mutation, Core mutation, readiness claim, or release
+claim occurred.

docs/STAGE5-TARGET-SANDBOX-STALE-CASE-STATE.md

@@ -56,6 +56,15 @@ no default Runtime activation.
 
 ## Remaining Movement Gate
 
+2026-06-17 custody preflight:
+
+- `docs/STAGE5-TARGET-SANDBOX-CUSTODY-PREFLIGHT.md` declares the original
+  target path historical proof context only.
+- `.sot/03-PROTOCOLS/CTO-CASE-STAGE5-TARGET-REPOSITORY-ADMISSION.json`
+  now sets `future_execution_authorized=false` and
+  `future_execution_requires_new_admission=true`.
+- The target sandbox was not moved in this slice.
+
 Movement remains deferred until CTO replaces the absolute live path dependency
 with archive-stable evidence or a new admitted target fixture, then reruns: