Arcgentic

Fail-closed rules

• If arcgentic CLI is not available, report installation failure instead of pretending Arcgentic is active.

• If the current thread is projectless or cannot create project-scoped role threads, stop.

• If .agentic-rounds/state.yaml records delegation source_thread_id as the Orchestrator session by mistake, do not create Planner. Repair only that field with:

  arcgentic v2-record-session \
    --state .agentic-rounds/state.yaml \
    --host codex \
    --role orchestrator \
    --thread-id <current-orchestrator-thread-id> \
    --title Orchestrator \
    --repair-current-orchestrator

• If .agentic-rounds/state.yaml cannot be created or validated, stop.

• If role threads cannot be created in the current project/workspace, stop.

• If a role thread is slow, send at most one status/constraint-tightening message. If it still does not return a valid RoleReturnSignal, stop with a role-timeout status. Do not continue the workflow in the Orchestrator.

• After dispatching a role prompt, call arcgentic v2-dispatch-role and end the Orchestrator turn. The Orchestrator resumes only when the pending role actively sends return information back to the Orchestrator thread.

• If arcgentic v2-return-signal rejects the role output, stop and report the rejected signal. Do not repair it by hand in the Orchestrator.

• Do not silently fall back to "Arcgentic-style" hand-written evidence.

• Do not treat "greenfield" or "empty repo" as permission for Orchestrator implementation.

• Do not verify, summarize, or inspect a previous closed round as the response to a new implementation request. Route the request to Planner first.

• Do not auto-dispatch Planner from project-level closed unless there is a new user request. Closed without a new request means the project workflow is stopped. Round-level PASS is not closed; it must advance through the stored project plan.

• Do not run ordinary coding work before Planner has produced or approved the round plan.

• Planner, Developer, Test, and Auditor must not mutate .agentic-rounds/state.yaml, run transition commands, dispatch roles, consume RoleReturnSignal, or close rounds. They write their role-owned artifacts and return natural-language output plus one arcgentic-role-return footer for the Orchestrator to consume.

• Role threads must not stop after acknowledging their role. They must complete role-owned work in the same turn, using tools as needed, before returning RoleReturnSignal. Developer, Test, and Auditor consume prior-role artifacts from project.arcgentic_v2.last_signal.artifacts.

• Role threads must actively wake the Orchestrator by sending their completed natural-language output and machine footer to the recorded Orchestrator thread. The Orchestrator must not poll role threads to discover completion.

• Planner must do discovery before handoff: search GitHub or equivalent public references for reliable comparable projects, scan local skills/plugins/MCP servers/connectors/tools, then write the selected references and tools into a detailed Markdown handoff. Each downstream role must read the handoff artifact named in the Orchestrator prompt before acting.

• Planner project-close returns must write a closeout artifact, create a local closeout commit, include artifacts.closeout and artifacts.commit, and use next_recommended_role: null. Closed projects are terminal idle unless the user provides a genuinely new work request.

• Auditor PASS fact rows must use lifecycle-stable evidence: committed artifacts, fixed git hashes, artifact file contents, state history, and test/build output. Do not use mutable live routing fields such as current_round.state, project.arcgentic_v2.last_signal.role, or project.arcgentic_v2.last_signal.state as PASS facts unless the command reads an immutable committed snapshot.

• Do not create source files, tests, handoff docs, self-audits, user-test reports, or external audit verdicts from the Orchestrator. Those belong to Planner, Developer, Test, and Auditor role threads.

Continue

Load and follow:

• codex-thread-orchestration for Codex V2 fixed-role threads.
• using-arcgentic for the general round-state vocabulary and state-machine rules.