# Visible Agent Runtimes

This reference applies only when Post.Build.Ship delegates optional peer review, implementation
assistance, factual checks, or QA. It does not require delegation.

When the host exposes visible Workspace panes, use those panes for delegated review, implementation,
or QA. Do not silently substitute a hidden agent. A returned pane ID establishes visibility even
when child workspaceMcp instrumentation is unavailable. Report the pane ID and any spawning or task
delivery failure accurately. This rule does not require delegation: Post. starts peer review only on
explicit request, Build. may delegate bounded implementation or QA, and Ship. may delegate bounded
review or QA while the primary agent owns final verification and commits.

Prefer a user-visible process whose capabilities match the bounded task. Command execution requires
repository access and a command-capable runtime. Review requires access to the exact artifact being
reviewed. Never claim a model, provider, permission, or capability that the runtime did not expose.

Create or select a process only when its complete packet is ready. Give it the repository path,
bounded objective, relevant evidence, ownership and mutation limits, expected output, and stop
condition. Keep raw QA logs in the command-capable process and return compact receipts.

Retain or close a visible process according to the host and user's instructions. Process lifecycle,
identity, availability, and closure data are operational context, not Authorizing User authority and
not a Build or Ship admission requirement.

If an optional reviewer or helper is unavailable, continue without it. If the only command-capable
route needed for required implementation or QA is unavailable, report the substantive execution
blocker. Do not confuse those cases.