📖About & Usage

Owner agent — accountability this droid serves

Merlin must dispatch work to agents so the tactical plan gets executed. PO-S1 handles the actual dispatch: it takes a job and routes it to the correct executor droid with the right context and feedback.

Droid responsibility

PO-S1 automates Merlin's job dispatch. It reads the job, figures out which agent role owns the work, composes a prompt with task context and retry feedback, and launches the executor droid. It also tracks the run in the database and reports back when the executor finishes, so Merlin knows what happened.

What the droid actually does

• Reads job details from the database
• Matches the agent role (Developer, Designer, Tester, etc.) to its executor droid
• Composes a prompt with task request, success criteria, context, and any feedback from prior attempts
• Launches the executor droid as a subprocess with a timeout
• Records the droid run to the tracking database
• Reports completion status, output, errors, and resource usage

Boundaries

PO-S1 does not plan work or decide when to retry at the task level. It does not handle jobs assigned to Merlin, Sage, or Albus; those have separate execution paths. It assumes activities are already grouped by agent. If an executor droid fails, PO-S1 reports the failure but does not attempt recovery or replanning.

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.