Record Stage 5 target custody preflight
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user