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

Record CTO target mirror blocker

Browse Source
This commit is contained in:
Svrnty
2026-06-17 09:09:20 -04:00
parent aae6d8afaf
commit 336f35b954
4 changed files with 87 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/LEGACY-INGEST.md
+8
View File
@@ -107,6 +107,14 @@ historical proof context only. The admission record sets
separate host-aware custody gate because the MacBook mirror can rehydrate root
paths unless policy is checked first.
2026-06-17 mirror blocker check: the MacBook source path
`/Users/jean-philippebrule/Steev/Cortex-OS/cto-stage5-target-sandbox` exists,
and `/Users/jean-philippebrule/Steev/push-cortex-os-to-steev-once.sh` does not
exclude `cto-stage5-target-sandbox/`. The custody preflight now records an
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.
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.