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

Reject CTO generated cache residue

Browse Source
This commit is contained in:
Svrnty
2026-06-18 13:52:34 -04:00
parent fd313768a5
commit 077227c8ab
2 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/LEGACY-INGEST.md
+13
View File
@@ -73,6 +73,19 @@ 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.
### Generated Cache Custody
Reference cluster:
- ignored `tools/__pycache__/` observed on `2026-06-18`
- `/home/svrnty/workspaces/cortex-os-retired/2026-06-18/cto-python-cache-preserved-135154/MANIFEST.md`
Decision: archive-only custody.
The useful idea is none; this is generated Python bytecode residue. Keep the
manifest reference only. Do not treat cache files as CTO source, evidence,
backend state, target-repo state, provider state, or historical intention.
### Stage 5 Target Sandbox
Reference cluster: