Record CTO target physical custody
This commit is contained in:
+16
-4
@@ -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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user