hermes/cto
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refresh CTO target sandbox gate evidence

Browse Source
This commit is contained in:
Svrnty
2026-06-17 02:20:33 -04:00
parent 1b29575bc1
commit 54a1842b90
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/LEGACY-INGEST.md
+6 -5
View File
@@ -89,11 +89,12 @@ The useful idea is an explicitly owned, noncritical, disposable target repositor
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.
- 2026-06-17 refresh: current path is not a Git repository.
- 2026-06-17 refresh: `python3 tools/validate_cto_stage5_target_sandbox_child.py` passes in the target.
- 2026-06-17 refresh: `python3 tools/validate_cto_child.py` passes in CTO while the root path exists.
- 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.
Movement gate: