ticket: split orchestrator automation phases

2026-06-07 12:57:40 +09:00
parent 9aa6e7d1ab
commit 550e0159ed
14 changed files with 337 additions and 1 deletions
@@ -8,7 +8,7 @@ priority: P1
 labels: [panel, orchestrator, ticket, automation, workflow]
 workflow_state: intake
 created_at: 2026-06-07T02:02:15Z
-updated_at: 2026-06-07T03:35:44Z
+updated_at: 2026-06-07T03:57:24Z
 assignee: null
 legacy_ticket: null
 ---
@@ -45,3 +45,45 @@ Decision:
 This keeps `workspace-panel-orchestrator-queue-automation` focused on routing behavior, queued notification handling, acceptance sequencing, and worktree/Pod orchestration rather than basic Ticket tool registration.

 ---
+
+<!-- event: decision author: hare at: 2026-06-07T03:56:37Z -->
+
+## Decision
+
+## Split into routing / agent execution / merge completion
+
+Split the Orchestrator automation work into three child tickets so the implementation can proceed in bounded slices while preserving the existing `worktree-workflow` and `multi-agent-workflow` contracts.
+
+Child tickets:
+
+1. `orchestrator-queued-ticket-routing`
+   - Panel Queue notification and Orchestrator routing entrypoint.
+   - `queued -> inprogress` acceptance before implementation side effects.
+   - First-pass blocker/dependency/conflict recording.
+
+2. `orchestrator-worktree-agent-routing`
+   - Use `worktree-workflow` and `multi-agent-workflow` as builtin/role guidance for accepted in-progress Tickets.
+   - Create child worktree, spawn coder/reviewer sibling Pods with correct scopes, run review/fix loop, and produce merge-ready dossier.
+
+3. `orchestrator-merge-completion`
+   - Merge authority boundary, reviewer approval, validation, merge, Ticket done/close, and worktree/branch/Pod cleanup.
+   - Dogfooding workspace may authorize merge/cleanup/close; conservative/default mode stops at merge-ready dossier.
+
+This keeps the umbrella focused on the end-to-end Panel Queue -> Orchestrator automation while allowing each operational slice to land independently.
+
+---
+
+<!-- event: decision author: hare at: 2026-06-07T03:57:24Z -->
+
+## Decision
+
+## Related planning-memory split
+
+Created `ticket-orchestration-plan-tool` for the lightweight Orchestrator memory/tool surface around Ticket ordering, dependency, conflict, capacity, and accepted-plan decisions.
+
+Decision:
+- Use Ticket/orchestration domain records for project-relevant routing decisions rather than session-lifetime Task tools.
+- Keep local Pod/session claims in the local role session registry.
+- Keep this separate from the core queued routing / worktree-agent / merge-completion slices so the first automation path can still rely on prompt/workflow sequencing while gaining a durable place for ordering/dependency decisions.
+
+---