Record CTO target physical custody

This commit is contained in:
Svrnty
2026-06-17 09:24:06 -04:00
parent 336f35b954
commit 3d64fb2563
6 changed files with 146 additions and 48 deletions
+16 -4
View File
@@ -83,9 +83,9 @@ Reference cluster:
- `.sot/03-PROTOCOLS/CTO-CASE-STAGE5-REPEATABILITY-PROOF-EVIDENCE.md`
- `tools/validate_cto_child.py`
Decision: keep the intention; defer movement.
Decision: keep the intention; physical custody complete.
The useful idea is an explicitly owned, noncritical, disposable target repository for Stage 5 proof. The target sandbox is not move-ready while CTO validators, admission records, approval text, replay proof paths, and target task state still depend on `/home/svrnty/workspaces/cortex-os/cto-stage5-target-sandbox`.
The useful idea is an explicitly owned, noncritical, disposable target repository for Stage 5 proof. The original target path is now historical proof context only, and the preserved payload is outside the umbrella.
Current evidence:
@@ -115,9 +115,21 @@ archive-stable evidence candidate for the target, but physical movement remains
blocked until mirror policy is updated or JP chooses a different MacBook source
custody policy.
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.
2026-06-17 physical custody result: the MacBook push script now excludes
`cto-stage5-target-sandbox/` with backup
`/Users/jean-philippebrule/Steev/push-cortex-os-to-steev-once.sh.bak.20260617-cto-target-exclude`.
The Steev target moved to
`/home/svrnty/workspaces/cortex-os-retired/2026-06-17/cto-stage5-target-sandbox-preserved-091700`
with `MANIFEST.md`. The preserved target validator passes from the preserved
path, pytest passes with cache provider disabled, and the original root path
stayed absent through the observed MacBook push window ending
`2026-06-17T09:18:23-04:00`.
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.
Current closure: the absolute live path dependency is closed for current
execution authority. Future Stage 5 execution still requires a new admission
record, new approval, current target validation, and fresh Harness evidence.
Rejected now: hard delete, cleanup-only target mutation, Case rerun, Harness rerun, provider mutation, target source mutation, Core mutation, Seed mutation, readiness claim, release claim.
## Rejection Rules
+66 -12
View File
@@ -6,7 +6,7 @@ Source: CTO-WORK-099.
## Result
Status: custody-preflight-complete.
Status: physical-custody-complete.
Original target path remains historical proof context only:
@@ -14,7 +14,13 @@ Original target path remains historical proof context only:
/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.
The target sandbox is preserved outside the umbrella at:
```text
/home/svrnty/workspaces/cortex-os-retired/2026-06-17/cto-stage5-target-sandbox-preserved-091700
```
The original Steev root path is absent after the observed MacBook push window.
## Admission Lifecycle
@@ -23,7 +29,7 @@ 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`
- `root_path_dependency`: `closed-preserved-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
@@ -31,13 +37,13 @@ text, current target validation, and fresh Harness evidence. The old
## Custody Decision
Physical relocation remains a separate host-aware custody gate. That gate must:
Physical relocation required a host-aware custody gate. That gate now records:
- 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.
- preserved target sandbox outside the umbrella with a manifest;
- preserved target validator passes from the preserved path;
- original root path absence after a MacBook push window;
- target ownership remains outside CTO and Core;
- no hard deletion.
No target source mutation, Case rerun, Harness rerun, provider call, runtime
start, browser open, branch mutation, Core mutation, readiness claim, or release
@@ -56,7 +62,8 @@ claim occurred.
- Physical movement is blocked until the mirror policy is updated or JP chooses
a different custody policy for the MacBook source.
This check is read-only. No MacBook script mutation occurred in this slice.
This preflight check was read-only. The later physical custody gate added the
`cto-stage5-target-sandbox/` exclude with a backup and `zsh -n` proof.
## Archive-Stable Evidence Candidate
@@ -89,5 +96,52 @@ Validators observed during this slice:
- `python3 -m pytest -q`: `11 passed`.
- `python3 tools/validate_cto_child.py`: `ok: true`.
The archive-stable candidate is enough to stop treating the path as execution
authority. It is not yet a physical custody move proof.
This candidate was superseded by physical custody proof.
## Physical Custody Proof
Preserved path:
```text
/home/svrnty/workspaces/cortex-os-retired/2026-06-17/cto-stage5-target-sandbox-preserved-091700
```
Manifest:
```text
/home/svrnty/workspaces/cortex-os-retired/2026-06-17/cto-stage5-target-sandbox-preserved-091700/MANIFEST.md
```
MacBook push script backup:
```text
/Users/jean-philippebrule/Steev/push-cortex-os-to-steev-once.sh.bak.20260617-cto-target-exclude
```
Applied rsync exclude:
```text
--exclude 'cto-stage5-target-sandbox/' \
```
Physical custody evidence:
- MacBook `zsh -n` on the patched push script: pass.
- MacBook one-shot push after the exclude: pass.
- immediate root absence after move: pass.
- observed root absence window:
- `2026-06-17T09:17:08-04:00`: absent.
- `2026-06-17T09:17:33-04:00`: absent.
- `2026-06-17T09:17:58-04:00`: absent.
- `2026-06-17T09:18:23-04:00`: absent.
- preserved target validator from preserved path: `ok: true`.
- preserved target pytest from preserved path with cache provider disabled:
`11 passed`.
- route-relevant relative sha256 list digest:
`ee69cd97b8349eaf800d25a13810ecd2436388e34cdaac84a4ee735366798d2c`.
- full relative sha256 list digest:
`487148fc897b810a1e3e0f96c86ed0b07e2e153bc5caa3679d26dd91e53c25b4`.
The original root path is no longer execution authority. Future Stage 5
execution still requires a new admission record, new approval, current
validation, and fresh Harness evidence.
+22 -14
View File
@@ -8,14 +8,19 @@ Source: CTO-WORK-097.
Status: stale-state-declared.
The target sandbox remains present at:
The target sandbox was originally present at:
```text
/home/svrnty/workspaces/cortex-os/cto-stage5-target-sandbox
```
The target sandbox is still not move-ready, but the old target-local Case task
state is no longer treated as active work.
The target sandbox is now preserved outside the umbrella at:
```text
/home/svrnty/workspaces/cortex-os-retired/2026-06-17/cto-stage5-target-sandbox-preserved-091700
```
The old target-local Case task state is no longer treated as active work.
## Current Evidence
@@ -41,7 +46,7 @@ from 2026-06-01 and 2026-06-02:
PR number.
These records are stale Case-local task residue. They are not current execution
authority, not active WIP, and not archive-stable completion evidence.
authority and not active WIP. They are preserved as historical residue in the physical custody manifest.
## Decision
@@ -54,24 +59,27 @@ The useful intention remains the Stage 5 proof pattern: admitted owned
noncritical target, explicit task contract, JP approval, Harness evidence, and
no default Runtime activation.
## Remaining Movement Gate
## Physical Custody Gate
2026-06-17 custody preflight:
2026-06-17 custody result:
- `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.
- The target sandbox is preserved outside the umbrella with a manifest.
- The original Steev root path stayed absent after a MacBook push window with
the `cto-stage5-target-sandbox/` rsync exclude active.
- The absolute live path dependency is closed for current execution authority.
Movement remains deferred until CTO replaces the absolute live path dependency
with archive-stable evidence or a new admitted target fixture, then reruns:
Custody validators rerun:
- `python3 tools/validate_cto_child.py`
- `python3 tools/validate_cto_stage5_target_sandbox_child.py`
- `python3 tools/validate_cto_stage5_target_sandbox_child.py` from the
preserved target path
- `PYTHONDONTWRITEBYTECODE=1 python3 -m pytest -q -p no:cacheprovider` from the
preserved target path
The future move must preserve the target path outside the umbrella with a
manifest. No hard delete, Core mutation, Harness rerun, Case rerun, provider
call, branch mutation, readiness claim, or release claim is allowed by this
record.
No hard delete, Core mutation, Harness rerun, Case rerun, provider call, branch
mutation, readiness claim, or release claim is allowed by this record.