cto/docs/STAGE5-TARGET-SANDBOX-STALE-CASE-STATE.md

CTO Stage 5 Target Sandbox Stale Case State

Local planning evidence only. Not Core authority. Not Runtime authority.

Source: CTO-WORK-097.

Result

Status: stale-state-declared.

The target sandbox was originally present at:

/home/svrnty/workspaces/cortex-os/cto-stage5-target-sandbox

The target sandbox is now preserved outside the umbrella at:

/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

Read-only checks on 2026-06-17:

• python3 -m pytest -q in the target sandbox: 11 passed.
• python3 tools/validate_cto_stage5_target_sandbox_child.py in the target sandbox: ok: true.
• python3 tools/validate_cto_child.py in CTO: ok: true.
• No live process matched the target path, ca run, or ca session outside the read-only process scan.
• The target path is not currently a Git repository, so there is no local Git worktree custody proof to preserve from that path.

The target-local .case/tasks/active/*.task.json set contains six stale records from 2026-06-01 and 2026-06-02:

• four records with status=active;
• two records with status=implementing;
• the two implementing records have agents.implementer.status=running with no completed timestamp;
• all six records have tested=false, manualTested=false, and no PR URL or PR number.

These records are stale Case-local task residue. They are not current execution authority and not active WIP. They are preserved as historical residue in the physical custody manifest.

Decision

Do not restart, continue, or mutate the stale Case tasks during umbrella purification.

Do not edit the target sandbox only to make cleanup look cleaner.

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.

Physical Custody Gate

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

Custody validators rerun:

• python3 tools/validate_cto_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

No hard delete, Core mutation, Harness rerun, Case rerun, provider call, branch mutation, readiness claim, or release claim is allowed by this record.