Profile semantics
Orcho separates two decisions that agent tools often blur together. A work-kind profile says what the task is — small_task, feature, complex_feature, planning, review, research or migration. An operating mode says how much verification and evidence the run should require — fast, pro or an explicit governed override.
01 Axis 1 · work kind
small_task takes the shortest implementation path. feature adds plan validation, implementation, review/repair and final acceptance. complex_feature adds stricter verification and a compliance gate. Planning, delivery audit, code review, research, refactor and migration profiles expose their own phase shapes.
02 Axis 2 · operating mode
fast is the default for small_task and research. pro is the default for feature and more analysis-heavy work such as complex_feature, planning, code review, audit, refactor and migration. governed is an explicit opt-in when the operator wants the strongest policy surface; it is never silently selected as the default.
03 Advisor
The profile advisor can recommend a work kind from task intent, but the operator keeps the decision. Project plugins and local configuration can tune workers, gates, isolation and verification without inventing a different meaning for the task.
Next step
Inspect the technical contract, watch the proof, or run Orcho on one task. The deeper layer is always one explicit step away.