Declare CTO Stage 5 target Case state stale
This commit is contained in:
@@ -95,10 +95,11 @@ Current evidence:
|
||||
- 2026-06-17 refresh: `tools/validate_cto_child.py` hard-codes the target path and admission record fields.
|
||||
- 2026-06-17 refresh: `.case/tasks/active/*.task.json` contains six active task records; two have `agents.implementer.status` set to `running` and no `completed` timestamp.
|
||||
- 2026-06-17 refresh: the target task records still use active or implementing states, so they are not archive-stable closure evidence.
|
||||
- 2026-06-17 stale-state declaration: `docs/STAGE5-TARGET-SANDBOX-STALE-CASE-STATE.md` records that target tests and the target validator pass, no live Case or `ca` process is present, and the six target-local Case records are stale residue rather than current work authority.
|
||||
|
||||
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.
|
||||
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