Role Baton Orchestrator

Role Baton Orchestrator

Purpose

Provide deterministic role sequencing for end-to-end tasks while preventing overlap and instruction drift.

Sequence (fixed, per ticket)

1. Manager
2. Collaborator
3. Admin
4. Consultant

Only one role may be active per ticket at a time. Multiple tickets may have different active roles concurrently.

Parallel dispatch

Manager may hand off N tickets to N different collaborators simultaneously. Each ticket carries its own baton independently. Constraints:

• Each collaborator owns exactly one ticket at a time.
• Admin merges are serialized (one PR at a time) to avoid conflicts.
• Collaborators pull latest main before creating PR.

Research ticket lifecycle

Research tickets skip branch/PR/merge. Baton sequence:

1. Manager: scope research question, assign collaborator (fleet LLM).
2. Collaborator: produce research, post findings on ticket.
3. Admin: review storage placement (wiki/research/), no merge.
4. Consultant: validate quality, close ticket.

Entry criteria

• Manager: task goal known.
• Collaborator: manager handoff exists.
• Admin: collaborator validation evidence exists.
• Consultant: admin execution evidence exists (or explicit N/A).

Stop conditions

• Missing required handoff artifact for next role.
• Contradictory constraints between role outputs.
• Failed mandatory gate without remediation path.

Handoff artifacts

• Manager -> Collaborator: scope, constraints, acceptance criteria, gate checklist.
• Collaborator -> Admin: changed surfaces + validation evidence.
• Admin -> Consultant: operational outcomes + governance/release status.
• Consultant -> Finish: risks, confidence, follow-up recommendations.

Required references

• repo-standards-router for standards/gates.
• workflow-self-anneal only for post-failure/process drift.
• Domain skills for specialized checks (release/docs/security/profile).

Consultant rating rubric (quick)

• 5: contract present but ambiguous; handoffs not reliably testable.
• 7: clear contracts; occasional ambiguity in escalation boundaries.
• 9: deterministic handoffs, explicit stop conditions, evidence-complete transitions.
• 10: same as 9 plus stable multi-session consistency with zero overlap drift.

Output format

ROLE_BATON_REPORT
context: <new-task|post-failure|pre-merge|pre-release>
scope: <code|ops|governance|mixed>

manager_handoff:
- scope:
- constraints:
- acceptance:
- gates:

collaborator_handoff:
- implementation_summary:
- validation_evidence:

admin_handoff:
- operations_executed:
- governance_status:

consultant_closeout:
- independent_findings:
- residual_risks:
- confidence: <low|medium|high>
- follow_ups: