# CTO Legacy Ingest

Local planning only. Not Core authority. Not a Core Protocol. Not active Runtime authority.

Source: CTO-WORK-097.

## Purpose

Legacy Ingest captures intention; it does not import implementation mass.

Use this file to decide which older CTO planning clusters still matter for the current child-local endgoal:

- Cortex governs.
- Hermes controls.
- CTO routes.
- Case executes.
- Harness proves.
- Target repo stays owned.
- Evidence records.
- Core promotes only through SOT route.

## Source Clusters Assessed By Intention

### Case Admission And Proof Contract

Reference cluster:

- `.sot/03-PROTOCOLS/CTO-CASE-SOURCE-ADMISSION-RECORD.md`
- `.sot/03-PROTOCOLS/CTO-CASE-ADAPTER-CONTRACT.md`
- `.sot/03-PROTOCOLS/CTO-HARNESS-EVIDENCE-INTERFACE-CONTRACT.md`
- `.sot/03-PROTOCOLS/CTO-CASE-FAILURE-FIXTURE-MATRIX.md`
- `.sot/03-PROTOCOLS/CTO-CASE-STAGED-PROOF-GATES.md`

Decision: keep the intention.

The useful idea is the proof shape: source admission, adapter boundaries, failure fixtures, staged gates, and evidence contracts. Do not preserve every intermediate scaffold if it only restates the same gate.

### Governed Execution Flow

Reference cluster:

- `CTO-WORK-066` through `CTO-WORK-071`
- `.sot/03-PROTOCOLS/CTO-GOVERNED-EXECUTION-REQUEST-PRD.md`
- `.sot/03-PROTOCOLS/CTO-GOVERNED-EXECUTION-APPROVAL-RECORD.md`
- `.sot/03-PROTOCOLS/CTO-GOVERNED-EXECUTION-EVIDENCE-CLOSEOUT.md`

Decision: keep the intention.

The useful idea is a governed request, explicit approval, execution evidence, and closeout. The target repository remains owned by its own route. CTO does not become a general execution authority.

### Hermes Visibility

Reference cluster:

- `.sot/03-PROTOCOLS/CTO-HERMES-CONTROL-SURFACE-PRD.md`
- `.sot/03-PROTOCOLS/CTO-HERMES-REAL-REFRESH-CONTROL-REPLAY-PRD.md`
- `.sot/03-PROTOCOLS/CTO-HERMES-WEBUI-CONTROL-PANEL-EVIDENCE.md`

Decision: keep the intention.

The useful idea is visibility and replay. Hermes may display proof posture, approval state, and blocked lanes. Hermes must not govern, promote, or mutate target repositories from this child workspace.

### Provider And Retention Work

Reference cluster:

- `.sot/03-PROTOCOLS/CTO-CASE-PROVIDER-DECISION-RECORD.md`
- `.sot/03-PROTOCOLS/CTO-CODEX-RETENTION-DRY-RUN-PACKET.md`
- `.sot/03-PROTOCOLS/CTO-CODEX-RETENTION-POLICY-PACKET.md`
- `.sot/03-PROTOCOLS/CTO-CODEX-RETENTION-ARCHIVE-EXECUTOR-PACKET.md`

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.

## Rejection Rules

- Do not activate Case as default backend.
- Do not mutate target repositories.
- Do not treat Hermes, Case, Pi, Codex, or any execution backend as Cortex OS authority.
- Do not promote child-local CTO text into Core without a governed Core route.
- Do not ingest duplicate planning drafts when a later validated closeout already captures the intention.

## Completion Stage

Stage: legacy intention captured for the main CTO planning clusters.

Remaining useful work: compress duplicate CTO planning surfaces after each cluster has an owner, validator coverage, and a current route decision.