Skip to content
This repository was archived by the owner on Aug 24, 2026. It is now read-only.

Latest commit

 

History

History
75 lines (38 loc) · 2.84 KB

CONTEXT.md

File metadata and controls

75 lines (38 loc) · 2.84 KB

Project Context

Terms

Auto

The orchestration policy and CLI that selects a Codex stage, skill, model role, and reasoning effort. Auto owns routing; selected skills own methodology.

Model role

A stable capability class (luna, terra, or sol) resolved to a configurable Codex model identifier at process launch.

Stage

One fresh Codex execution with a single responsibility, explicit access level, selected skill, and structured output contract.

Context Packet

A durable, validated stage output and source record used by ContextAssembler to derive target-specific Stage Context.

Proposed Plan

The structured output of the plan stage. It informs approval but is not executable authority.

Approved Plan

The immutable version-1 proposed-plan snapshot pinned to a run at approval. It is the durable authority for downstream execution and cannot be rewritten by a stage.

Plan Reference

The approved-plan version and its sha256: canonical-JSON digest. Downstream context and results use it to prove that they refer to the pinned plan.

Stage Context

A compact, typed, target-specific projection of the approved plan and relevant current state. It is neither a transcript nor a source of truth.

Review finding

A structured review issue with a P0-P3 priority, concrete evidence, and required change. P0/P1/P2 block completion; P3 is advisory.

Unresolved Finding

A P0/P1/P2 review finding present in the latest completed review. A finding omitted by a later clean review is resolved; attempt counts never control the review-and-revision loop.

Revision cycle

The durable review-to-implementation transition created by an unresolved finding. Attempt history stays in SQLite while the next stage receives only its bounded Stage Context.

Run ledger

The durable SQLite record of a task, its classification, selected stages, events, outputs, and current state.

Escalation

A structured request emitted when a stage cannot continue without a different role or a human decision. Evidence, not additional effort alone, determines the route.

Route receipt

The explainable record of which policy rule selected a stage, skill, model role, and reasoning effort.

Benchmark

A durable paired Auto-versus-Normal experiment rooted at one immutable commit.

Trial and variant

A trial is one isolated candidate worktree. Its variant is either the full Auto route or one ordinary direct Codex run.

Participant metrics and evaluator metrics

Participant metrics measure the candidate run. Evaluator metrics measure the separate blind review and never count toward either candidate.

Invalid trial

A trial with no valid quality observation because its participant or evaluator failed, or because its same-repetition peer is invalid or missing. Existing participant evidence remains durable even when paired evaluation is skipped.