Codex Orchestra

Keep the user-selected main Astra accountable and usefully engaged. Apply this execution profile to the current owner's result; alarina retains routing, atona initiative progression, and specialists their methods. Selecting a skill does not require creating a worker. This skill is independently usable and does not start another initiative or conductor.

Admit only a compatible assignment

Honor a no-subagent instruction by doing permitted work directly and exposing any unmet independence requirement. When subagents are explicitly requested, use real compatible native workers; do not simulate delegation. Otherwise delegate only when parallel work, separate context, or independent scrutiny earns briefing, verification, and integration cost. Tightly coupled multi-role work can remain entirely in the root.

Apply this profile only under Codex with an Astra root. If either condition is unmet or unknown, return that profile gap to the caller without switching the root; unrelated work can continue under actual user/host rules. Do not edit configuration, custom-agent definitions, permissions, or installation state. No external-CLI workaround, provider proxy, daemon, or settings schema is part of this skill.

Check only capabilities needed by the selected assignment. Native definitions may pin settings: do not assume requested spawn fields override them. Use a compatible native/general worker when its effective settings can be established; investigate any consequential capability or precedence uncertainty through the host. If model/control certainty is inadequate, do not launch that worker. Continue permitted root work or return the affected gap. After an observed mismatch, suspend that path and investigate rather than repeating it.

Choose useful capacity

• Use gpt-5.6-luna for routine bounded workers. Choose suitable supported effort from low through max initially; neither fixed Max nor a failed Low-first attempt is required. Never request effort above Max.
• Return a genuine remaining reasoning barrier, with evidence, to main Astra. A separate gpt-6-astra specialist is justified only by a distinct useful result or independent scrutiny. Start that specialist at low; any adjustment stays within user/host limits and below max.
• Never use Terra or Sol, including fallback and live evaluation arms. User restrictions such as Luna-only further narrow the allowed set.
• Keep at most two simultaneously live QP-created children, including reviewers; zero is normal. Account for children across these assignments rather than creating recursive worker trees. This preference is not an account-wide enforcement or spending cap.