Agent Pipeline

OMP Native Agent Pipeline

Use for /auto go SPEC-ID [--execution-owner omp|orca]. This entrypoint selects work and context; open only the reference needed for the current step.

Execution Decision

Work in the current session by default. Dispatch only genuinely independent slices, a necessary specialist review, or work that needs isolated context. File count and line count do not justify delegation. Keep dependent or same-file work sequential; one migration-numbering lane has one writer.

A verified low-risk compact change contract omits separate planning and test scaffold dispatch: implementation still starts with the relevant failing test, then validation and review run. Missing, ambiguous, or escalated authorization keeps the full route. Report the actual route_phase_set from auto pipeline run, not an imagined phase checklist. Explicit --solo, --team, and --multi requests must retain their requested semantics.

Execution Owner

Choose exactly one DAG owner before any dispatch: --execution-owner omp|orca. Omission selects omp. Reject duplicate, aliased, or conflicting owner flags; never retry a failed explicitly selected owner as another owner.

• Owner omp: this session owns progress through native task, hub, and todo. --solo keeps work in this session; --team requests a native batch with explicit responsibilities. The two flags conflict.
• Owner orca: only an explicit --execution-owner orca selects it. First run and read orca skills get orchestration --full; the Orca Run owns the DAG. Do not create a competing OMP task or progress DAG. --team and --solo conflict with this owner.
• --multi requests risk-tiered provider-diverse evidence, not a second DAG.

auto pipeline run SPEC-ID --platform omp --execution-owner orca performs the integrity check and records pipeline_execution_owner_receipt.v1 before any worker session. The body-free .autopus/pipeline-state/<SPEC-ID>.execution-owner.json records owner, source, identity, and verification status.

Native Dispatch

Before dispatch, inspect the tools actually exposed by this runtime. Use their current schemas rather than copying static payloads. If the selected topology requires an unavailable tool, report that blocker; never simulate dispatch.

OMP registers five agents: scout, reviewer, security-reviewer, task, and sonic. There is no Autopus-specific agent to select, so pick by what the work needs:

• task runs planning, implementation, debugging, test authoring, and UX work. It is the default for every writing slice; omitting the agent selects it.
• scout is read-only exploration only. Never give it work that writes.
• reviewer and security-reviewer keep their built-in review boundaries; use them for review and security findings, not for implementation.
• sonic is only for an explicit mechanical request. Never route reasoning, planning, validation, or review to it.

The role a worker plays belongs in its assignment text, not in an agent name. State the responsibility, scope, and exit condition in the task itself.

Batch independent owned slices together. Native OMP owns isolated worktree creation, integration, and cleanup. Request isolation only if the current task schema exposes it; do not manually merge or remove its worktrees.

Each worker receives scope, forbidden paths, acceptance criteria, and only its needed context. Request the five-field result contract: owned_paths, changed_files, verification, blockers, next_required_step. Use native schema validation where supported; worker assertions are not execution proof. Record actual dispatch count and the native agents used. Follow up with the same revivable worker through hub; an isolated worker whose workspace has been released needs a new assignment. Only the parent owns todo.

A worker that stops at its turn limit returns a partial result; the turn-budget rule every assignment carries (references/delegation.md, Worker hygiene) keeps that rare. Never treat a partial result as a completed phase or feed it to the next phase. Follow up once with a narrowed instruction (finish and write the artifact, minimal further exploration), through hub or as a new assignment as above; if that run is partial again, stop and hand the phase to the user with what was produced.