Svrnty
69 lines
4.7 KiB
Markdown
69 lines
4.7 KiB
Markdown
# Cortex OS CTO Endgoal
|
|
|
|
Endgoal: Maintain child-local CTO planning for governed execution routing, adapter design, transportability, and validation scaffolds without Core authority, Runtime authority, backend ownership, vendor-source authority, execution-backend authority, or readiness claims.
|
|
Authority: child-local CTO planning workspace; Core authority lives in `/home/svrnty/workspaces/cortex-os/core`.
|
|
|
|
## Universal Cortex OS Agent Contract
|
|
|
|
- Treat this file as route-local instruction after parent `AGENTS.md` files and before chat memory.
|
|
- Start broad or ambiguous work with `cortex graph context`; use it only as Derived State, then read this repo's local files.
|
|
- Before edits, read `AGENTS.md`, `README.md`, and `WORKBOARD.yaml`; keep writes route-local unless a governed Core route explicitly authorizes promotion.
|
|
- Run this repo's named validator before handoff or done claims; use stronger proof only for runtime, provider, secret, memory, profile exposure, branch, release, or readiness effects.
|
|
- Record proof and handoffs as refs-only artifacts. Do not write Hindsight memory, Core SOT, sibling repos, or live runtime state unless explicitly authorized by the owning route.
|
|
|
|
## Repo-Custom Agent Contract
|
|
|
|
CTO owns child-local execution-routing planning, adapter design, transportability briefs, staged proof gates, target-repo admission templates, approval packets, evidence interface contracts, and validation scaffolds. It must not own Core truth, Runtime authority, Host Runtime authority, backend ownership, vendor-source authority, external developer repo authority, execution-backend authority, provider authority, target-repo mutation authority, Profile Exposure authority, product readiness, release authority, or production readiness.
|
|
|
|
Allowed proof is child-local and refs-only unless an explicit governed route approves a stronger gate: planning docs, WorkBoard entries, target-admission records, approval packets, harness evidence contracts, validator output, and git commits. This repo may inform CTO routing and execution planning only through the owning route; it does not activate Case as default backend, mutate target repositories, mutate vendor source, start Runtime, call providers, read secrets, broaden profile exposure, write Hindsight memory, mutate Core, mutate Seed, mutate sibling repos, mutate OpenDesign, claim readiness, publish, deploy, or release.
|
|
|
|
## 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.
|