2.6 KiB
Cortex OS CTO Context
This context defines local product language for the Cortex OS CTO planning workspace. It is child-local glossary language and does not create Core authority.
Language
CTO Product Surface: A governed operator-facing product area for delegating bounded code-change work while preserving Cortex OS authority, evidence, and approval rules. Avoid: CTO app, autonomous developer, coding bot
Case Candidate Backend: The proposed Case-based execution backend for real-repo code-change work, admitted only after adapter proof, validator coverage, and governed routing. Avoid: Case default, Case authority, replacement kernel
CTO Harness: The adapter conformance and evidence validation module that normalizes backend behavior into a stable CTO evidence interface. Avoid: execution authority, final reviewer, product readiness proof
Harness Evidence Interface: The stable artifact and event contract used to compare backends and prove bounded execution results. Avoid: loose evidence bundle, backend logs, success claim
Target Repository: The owned source repository receiving bounded, approved, evidence-producing code changes. Avoid: vendor source, hidden workspace, disposable scratch by default
Copied Repository Fixture: A runtime copy of an owned local source repository used to prove backend behavior without mutating the source repository or a Target Repository. Avoid: Target Repository, live repo, external developer source
Hermes Control Surface: A Hermes-facing summary and replay surface for CTO Harness state, approval context, and evidence links. It controls visibility and interaction but does not govern. Avoid: Core authority, runtime default switch, backend approval source
Governed Workflow Delegation: A bounded real coding task routed through CTO, approved through Hermes/operator policy, executed by an eligible backend, and accepted only through CTO Harness evidence. Avoid: autonomous default execution, unmanaged Case task, direct repo mutation
Core Promotion Decision Packet: A child-local CTO artifact that maps validated CTO evidence to a future governed Core decision route. It may request Core review, but it does not grant Core authority or runtime default activation. Avoid: promotion approval, Core authority, runtime default switch
Core Route Admission Guard: A child-local CTO guard that blocks a future Core review request when Core has active or conflicting work. It records route readiness checks, but it does not reserve Core, mutate Core, or override Core Sequence Protocol authority. Avoid: Core reservation, Core work claim, promotion authority