# Cortex OS CTO Endgoal ## Pickup Route: `cto` at `/home/svrnty/workspaces/cortex-os/cto`. Endgoal: maintain child-local CTO planning that can route governed execution work without becoming Core authority, a Runtime, or a backend owner. Stage: CLEAN after `python3 tools/validate_cto_child.py` passes. Clean score: 100. Authority boundary: child-local CTO planning workspace only; not Core authority, Runtime authority, Host Runtime authority, backend owner authority, vendor-source authority, external developer repo authority, execution-backend authority, or readiness authority. Validator: `python3 tools/validate_cto_child.py`. Legacy-work relation: old CTO planning, adapter design, transportability, Case/Hermes/Pi/Codex/backend, and validation scaffold work is reference-only unless `docs/LEGACY-INGEST.md` admits the intention. Distill route and planning contracts; do not import vendor source, backend state, runtime behavior, or implementation mass because they exist. Read `docs/LEGACY-INGEST.md` before broad cleanup, restart, or old-work ingestion. It captures the intention behind mature CTO clusters and rejects implementation mass that does not serve the current endgoal. This workspace is a child-local planning workspace for the Cortex OS CTO product line. It is not Cortex OS Core authority. It is not a Runtime. It is not a Host Runtime. ## Authority Order 1. `/home/svrnty/workspaces/cortex-os/core` active SOT. 2. `/home/svrnty/workspaces/cortex-os/core/AGENTS.md`. 3. This file. 4. `README.md`, `WORKBOARD.yaml`, local `.sot/`, and local tools. 5. Chat/session memory. ## Workspace Classification Use this workspace for child-local CTO planning, adapter design, transportability briefs, and validation scaffolds. Do not claim Core authority from this workspace. Promotion into Core requires a governed Core route. ## Editing Rule Before editing, classify the work and keep it inside this workspace unless Core explicitly routes promotion. After editing, run: ```bash python3 tools/validate_cto_child.py ``` For governance text, follow Core caveman prose discipline. ## Protected Boundaries - Do not mutate `../core/` from this workspace. - Do not mutate vendor source. - Do not mutate external developer repositories. - Do not create Runtime behavior without a Core-approved route. - Do not treat Case, Hermes, Pi, Codex, or any execution backend as Cortex OS authority.