vanillagreencom/kendex/orch

Orchestration

Load mailbox for takeover; github, worktree and linear before use. Dev and reviewer skills call orch scripts.

MODE SWITCH: you are the orchestrator. Delegate every implementation, review, and QA task to a specialist sub-agent. Never edit code unless the user explicitly asks, or the item runs the micro tier (workflows/micro.md), whose runner makes the edit itself.

The Cycle

Get the issue → dev implements → publication, review and fixes in the order from pr-order --help → required CI and review gate → merge.

• Bounded loops. A fix round addresses blockers only, and the same pass declines or tracks every fix suggestion (workflows/review-pr.md § 4); re-review narrows to the fix diff, the domains it touched, and the class of every defect it fixed (reviewer/SKILL.md § Re-Review Rounds); two consecutive rounds with no new blocker end the review; workflows/review-pr.md § At The Cap sets the cap, cap 0 and a fix round's own regression.
• Finding conduct. Apply reviewer's decision flow, recurrence rule and filing bar.
• Scope cuts. A reviewer or orchestrator can choose a cut round. A round whose only findings are scope or wording asks ends the review: reply, resolve, push nothing, merge through the gate.
• Ask gates. Which questions reach the user is references/communication-modes.md; nothing outside that file narrows or widens the set. Use communication for prose under the mode ORCH_USER_MODE names. That ask set holds whatever ORCH_DECISION_MODE says. Merge asks unless ORCH_MERGE_AUTONOMY=auto, which merges without asking only when every merge gate is green. In a lane every ask gate is lane-mail, never the harness question tool: references/skill-rules.md § Coordination.
• Post-PR autonomy. After a PR exists, ORCH_DECISION_MODE=auto-recommended takes and logs the continuing option while a bounded wait, retry, or triage round remains. ask presents the listed choice. workflow-state head-budget take owns automatic retry spending, starting the count over on a changed head for review-wait only. At a cap, workflow-state post-pr-stop record atomically persists the named stop and renders its matching Markdown comment; the workflow posts that file to the PR and returns the stored stop. A nested caller uses record-if-empty so a precise upstream stop wins. Every continuing action clears the stop with workflow-state update. Initialize the resolved state key before these transitions. ORCH_MERGE_AUTONOMY controls merge consent only.
• The overseer reads results. It accepts green lane checks and CI without reruns, prepare, commit, push or merge grants, or a shared validation slot. Only local micro runs here; its commit chain validates it. Green lanes with user merge consent arm auto-merge and own its wait per workflows/merge-pr.md. Dev test-only validation-ceiling reports end validation. Lanes tick branch boxes with proving artifacts. It ticks post-merge boxes only after reading proving artifacts at their revision and conditions: test output, screenshot, measured figure or deployed screen. Lane summaries are no proof. A container closes when its last child is Done or Canceled, through container-close; an outcome to read lives in its own child. When evidence is due or contradicted, it reads it to narrow, replace or stop the failed intervention. A fix item is not the default. It gives no model or account instructions. Lanes keep launch models and launch no lanes.
• Item work stays in lanes. A fleet is hosted when lane-host resolve prints anything except local. Overseers share its control VM for coordination. The overseer does no item work there: no worktree, item branch, dev, review or fix agent, validation, build, install or test run. Every item round goes to its branch's lane. A control-host subagent (sweep, triage verifier, measurement or research) reads without bulk writes: stream archives, or extract each into its own scratch subdirectory and remove the extraction before the next. Before extraction, read its uncompressed size and the volume's free space; if less than 3 GB would remain, stop and report to the overseer without extracting. No history-wide content read (git log -S or -G, --all -p, or any command reading every blob): lazy fetch in a partial clone can fill disk. Search via gh search code, the GitHub API, or a lane. No busy waits (/dev/zero, /dev/urandom, spin polls) on the shared host. Wait with one bounded background command and completion notice, or watch events. Every control-host subagent brief includes this rule. Its scratch location is an empty subdirectory (tmp/<run>/<agent-topic>/) only that subagent removes, never one the overseer's background jobs read. Fleet guards read command blocks. Refresh follows the consumer's owner. No --refresh-only exception.
• Acceptance is artifact-based. A round closes on a validated on-disk artifact plus git/tracker state, never on a return message.
• Rules reload after a rebase. Before a step that can rebase the branch (worktree-push, worktree create --reuse, a restack), bind git -C [WT_PATH] rev-parse --verify HEAD as [BOUND_HEAD]. A step that moves it is followed at once, before any validation, publication or arm, by git -C [WT_PATH] diff --no-renames --name-only [BOUND_HEAD] HEAD -- <each loaded file's repo path> and a re-read of each listed file at [WT_PATH]/<path>, with the deleted-path rule of dev SKILL.md § Round Contract.
• A lane is quiet. ORCH_LANE_OUTPUT decides what a lane prints and where a filled <output_format> block goes: references/skill-rules.md § Lane Output.

Commands

Route <command> [args] to its workflow and follow Workflow Execution.

`start` routing. github OWNER/REPO#N → TRACKER=github, ISSUE_ID=issue-N, keep OWNER/REPO for the API; otherwise Linear unless the id starts with issue-. A cwd whose git common dir differs from .git is a worktree → workflows/start-worktree.md; otherwise workflows/start.md.

Scripts

.agents/skills/orch/scripts/<script> [args]