agent-workflow-orchestrator

name	agent-workflow-orchestrator
description	Run or resume the full lifecycle from request clarification through reviewed planning, freeze, authorized execution, per-task audits, and final proof.

Agent Workflow Orchestrator

Use agent-workflow-orchestrator to drive the complete lifecycle. The controller is host-neutral: skills define semantics, while each host adapter owns native questions, approvals, tool calls, agent launch, waiting, cancellation, and telemetry.

Lifecycle

1. Load existing durable state when present. Do not reconstruct authority from chat.
2. Clarify only decisions that materially change behavior, scope, safety, architecture, ownership, evidence, or external authority.
3. Route planning to agent-first-planning.
4. Route every candidate specification or plan to independent review through audit-agent-plan; refine until the freeze verdict passes or blocks.
5. Freeze only reviewed matching inputs.
6. Compile packets with agent-plan-to-workers.
7. Respect execution mode: plan-only, approval-required, or auto-after-freeze.
8. Launch only dependency-ready packets within frozen parallelism.
9. Run controller-owned validation before launch and after attempts when the plan requires it.
10. Audit every task attempt with audit-plan-implementation before acceptance.
11. Route implementation/test/evidence defects to bounded remediation. Route plan gaps, write-set gaps, architecture changes, or contract changes to reopen and refreeze.
12. After all required tasks are accepted, run final implementation audit and publish completion only from a reproducible proof.

State Rules

• Immutable authority: plan manifest, plan lock, frozen packets.
• Mutable runtime: workflow state, journal, task results, task reviews, evidence receipts, final audit.
• Every mutation needs an operation id, expected revision, source revision, and reason.
• Bounded waits only. On timeout, request cancellation through the host adapter and record a conservative block.
• Budget exhaustion, missing receipts, stale evidence, or unverifiable telemetry cannot produce a pass.

Context Policy

• Keep the latest user instructions and active packet verbatim.
• Summarize older context into structured state.
• Drop tool dumps and intermediate data after extracting decisions, evidence ids, hashes, exit codes, and blockers.
• Prefer deterministic validators before semantic review.
• For 4k-strict/8k/16k/32k/64k hosts, render/check context with small-context-profile.v1; overflow must split, request larger context, or block, never silently truncate.

Output

Return the next typed action, current run phase, locked tasks, active blockers, accepted evidence, remaining budget, and concrete next command or host action.