# 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.