Record CTO Stage 5 target reconciliation

This commit is contained in:
Svrnty
2026-06-16 23:10:36 -04:00
parent 5f2d333648
commit 1b29575bc1
+28
View File
@@ -73,6 +73,34 @@ Decision: keep the intention with caution.
The useful idea is explicit provider admission and metadata-only retention hygiene. Do not copy secrets, raw transcripts, or provider runtime behavior into CTO. Archive and deletion remain approval-gated.
### Stage 5 Target Sandbox
Reference cluster:
- `/home/svrnty/workspaces/cortex-os/cto-stage5-target-sandbox`
- `.sot/03-PROTOCOLS/CTO-CASE-STAGE5-TARGET-REPOSITORY-ADMISSION.json`
- `.sot/03-PROTOCOLS/CTO-CASE-STAGE5-OWNED-NONCRITICAL-REPO-PRD.md`
- `.sot/03-PROTOCOLS/CTO-CASE-STAGE5-REPEATABILITY-PROOF-EVIDENCE.md`
- `tools/validate_cto_child.py`
Decision: keep the intention; defer movement.
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`.
Current evidence:
- current path is not a Git repository.
- `python3 tools/validate_cto_stage5_target_sandbox_child.py` passes in the target.
- `python3 tools/validate_cto_child.py` passes in CTO while the root path exists.
- `tools/validate_cto_child.py` hard-codes the target path and admission record fields.
- `.case/tasks/active/*.task.json` still contains `active` and `implementing` task states.
Movement gate:
Move or archive only after CTO replaces the absolute live path with archive-stable evidence or a new admitted target fixture, closes or declares stale the active Case task state, 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.
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.
## Rejection Rules
- Do not activate Case as default backend.