Pepeye

Coordinate several owned results toward one accepted outcome. The current lead owns workflow progression, integration, user decisions, and final judgment. Skills keep their own methods, evidence contracts, and authority boundaries; native workers are execution contexts underneath them.

Orchestration model

Use the smallest orchestration scale that fits the work:

• assignment — one bounded execution context with one primary skill, optional supporting capabilities, exact scope/authority, and an expected result;
• workflow — one accountable lead composes several assignments/stages with dependencies, branches, skip conditions, independence boundaries, and completion evidence;
• program — a workflow whose correct continuation must survive loss of the current lead/session. Durable orchestration state is justified only at this scale.

A workflow owner is not a stage owner. Sequencing alaga, atunwo, architect, or another skill does not copy or replace that skill's method. Put workflow-specific behavior in the dispatched assignment, never in the selected skill definition.

Use alarina when the next semantic owner or useful route is genuinely ambiguous. Do not route every declared workflow stage through it.

Compose assignments

Use native subagents when parallelism, focused context, investigation, or independent judgment materially helps. Work directly on small localized tasks.