Factory supervision

Execute an already chosen Factory route across agent boundaries. The reader is a Coordinator, Slice Owner, or Goal Validation Owner. The outcome is one settled assignment whose workspace, authority, evidence, and cleanup remain traceable across harnesses.

This skill owns execution placement and supervision. It does not choose product behavior, accept a design, change a slice, update the project profile or goal map, or replace pursue-goal and the role skills.

Prepare the assignment

1. Identify the initiating owner, target role, accepted route, and terminal result expected by that route. Reject a request that gives the target more Factory authority than its role permits.
2. Require one current coordination envelope and one bounded assignment. Read the execution contract for required identities, topology, and capabilities. For a Git-backed filesystem assignment, also read and apply the preflight contract. Reject superseded identities instead of merging them.
3. Inspect the available runtimes and target harnesses. Follow explicit human direction or the accepted execution plan. Otherwise choose only among harnesses that satisfy the role and supervision contract. Do not infer capability from a model or product name.
4. Choose one adapter before creating state:
   • When Orca owns the worktree, terminal, or coordination state, read the Orca adapter.
   • Otherwise read the native harness adapter.

Completion criterion: the assignment has one owner, one role, current identities, a valid workspace and resource lease, a capable target harness, and one selected adapter.

Preserve the topology