v0.8.68 architecture: Fleet / Workflow / Lane / Runtime product model (canonical tracker)

[Hmbown]

Purpose

Canonical tracker for the approved CodeWhale orchestration vocabulary and separation of concerns. This issue links the implementation phases and prevents Fleet, Workflow, Lane, and Runtime from collapsing into one concept.

Docs: docs/AGENT_WORKFLOWS_0868.md (merged via PR #4163)

Canonical vocabulary

Term	Meaning	Owns
AgentProfile	Saved model/persona/tool config	provider, model, thinking, instructions, tool posture
Fleet	Named roster of AgentProfiles (WHO)	role → profile bindings; resolves roles → AgentProfiles
Workflow	Graph/sequence of work steps assigned to fleet roles (WHAT ORDER)	phases, tasks, gates, handoffs — not model/persona config
Lane	A running workflow instance for one issue/goal (RUNNING INSTANCE)	lane id, issue binding, status, logs, attach target
Runtime	Execution backend (WHERE/HOW)	tmux+worktrees, remote VM, inline subagents, CI

Principles (non-negotiable)

• Do NOT make Fleet a task runner.
• Do NOT make Workflow own model/persona config.
• Workflow steps reference fleet roles (e.g. scout, implementer, reviewer); Fleet resolves roles → AgentProfiles; Runtime executes resolved agents.
• tmux durability (sessions, attach, reconnect) belongs in Runtime, not Fleet.

Data flow

Workflow step (role: scout)
  → Fleet.resolve("scout") → AgentProfile
  → Runtime.spawn(profile, worktree?, backend=tmux|inline|vm|ci)
  → Lane records run instance + stream-json logs

Agreed CLI shape

codewhale workflow run stopship --issue 4090 --fleet v0868-stopship --runtime tmux
codewhale lane list | status | attach | logs | stop

Implementation phases

Phase	Theme	Issue
1	Runtime + Lane CLI	#4176
2	Workflow calls Fleet roles	#4177
3	Gates + handoffs	#4179
Dogfood	Stopship as fleet-backed lane	#4178

Recommended execution order

1. Stopship TUI fixes — v0.8.68 TUI: repeated Ctrl+C re-prompts instead of exiting in PTY/raw-mode path #4090, Fleet setup modal is provider-scoped instead of a role/profile roster editor #4093, Sub-agent detail panel is empty and can freeze the TUI during active work #4094 (unchanged priority; manual or inline-runtime)
2. Phase 1 — v0.8.68 Phase 1: Lane CLI + Runtime backends (tmux, worktrees, stream-json logs) #4176 (Lane CLI + Runtime adapters)
3. Phase 2 — v0.8.68 Phase 2: Workflow steps reference Fleet roles (not raw prompts/profiles) #4177 (Workflow → Fleet role resolution) + v0.8.68 remaining: make AgentProfile canonical for Fleet rosters #4111/v0.8.68 2.19: make AgentProfile the canonical Fleet actor contract #4136/v0.8.68 2.20: let Fleet profiles save provider model and thinking #4137 (AgentProfile canonical)
4. Phase 3 — v0.8.68 Phase 3: Workflow gates and handoffs between Fleet roles #4179 (gates/handoffs) + v0.8.68 WhaleFlow: verification gates (compile, test, lint, review as post-agent hooks) #4013 (verifier role gates)
5. Dogfood — v0.8.68: Stopship workflow as fleet-backed lane (dogfood #4090/#4093/#4094) #4178 (stopship workflow via new CLI)
6. Workflow UI — v0.8.68 Workflow: product-readiness tracker #4038, v0.8.68 remaining: Workflow automatic launch and unified activity UI #4110, v0.8.68 2.3: default parallel write workflow children to worktree isolation #4120–v0.8.68 2.18: standardize Workflow phase agent task vocabulary #4135 (panel/events; deferred until stopship green)

Related trackers

• v0.8.68 Workflow: product-readiness tracker #4038 — Workflow product-readiness umbrella
• v0.8.68 remaining: make AgentProfile canonical for Fleet rosters #4111 — AgentProfile canonical for Fleet rosters
• v0.8.68 remaining: Workflow automatic launch and unified activity UI #4110 — Workflow automatic launch + unified activity UI
• v0.8.68 execution board: lane order, dependencies, and agent protocol (canonical packet) #4092 — Milestone triage / next-agent packet
• v0.8.68 TUI: repeated Ctrl+C re-prompts instead of exiting in PTY/raw-mode path #4090, Fleet setup modal is provider-scoped instead of a role/profile roster editor #4093, Sub-agent detail panel is empty and can freeze the TUI during active work #4094 — Active stopship (priority unchanged)
• PR feat(workflows): v0.8.68 agent execution lanes and milestone sync #4163 — Agent workflow playbook + lane JS files

Acceptance

• Phase issues (v0.8.68 Phase 1: Lane CLI + Runtime backends (tmux, worktrees, stream-json logs) #4176–v0.8.68 Phase 3: Workflow gates and handoffs between Fleet roles #4179, v0.8.68: Stopship workflow as fleet-backed lane (dogfood #4090/#4093/#4094) #4178) linked from this tracker.
• All related issues cross-link here and to docs/AGENT_WORKFLOWS_0868.md.
• No open issue describes Fleet as owning tmux sessions or Workflow as owning provider/model config.