MAP Turn-Taking Session
Multi-Agent Protocol with turn-taking. Two agents collaborate with role rotation.
Website Source Model
Actual page source: Website aggregate projection layer in MPLP_website/lib/content/flows.ts.
Upstream provenance: IDs, titles, and boundary classification come from tests/golden/flows/registry.ts; per-flow scenario detail is summarized from the upstream asset tests/golden/flows/map-flow-01-turn-taking/README.md. The Docs page is a secondary reference at verified flow reference.
Goal
Validate MAP round_robin mode with sequential turn execution.
Success Criteria
Turns execute sequentially, roles rotate correctly.
Sequence
Execution Steps
Website summary of the scenario sequence represented by this flow.
Session Init
MAP session with round_robin mode.
Role Assignment
Agent A (planner), Agent B (reviewer).
Turn 1: Plan
Planner creates initial plan.
Turn 2: Review
Reviewer evaluates plan.
Turn 3: Revise
Planner revises based on feedback.
Session Init
MAP session with round_robin mode.
Role Assignment
Agent A (planner), Agent B (reviewer).
Turn 1: Plan
Planner creates initial plan.
Turn 2: Review
Reviewer evaluates plan.
Turn 3: Revise
Planner revises based on feedback.
Profile Reference
Profile Flow Scope
This Website summary reflects the evaluated scope of a profile-level reference scenario. It is not part of the v1.0 core published boundary.
Collab Module
Collab mode MUST be round_robin for turn-taking.
Role Module
Roles MUST rotate correctly between participants.
Plan Module
Steps MUST respect turn order from Collab.
Validation
Failure Conditions
This profile-level reference flow should be treated as failed if any of the following conditions occur during evaluation.
Turns do not execute sequentially.
Role rotation is incorrect.
Concurrent execution in round_robin mode.
Collab participant binding fails.
Profile-Level Reference Boundary
This scenario is published as a profile-level reference flow. It informs SA or MAP profile evaluation, but it does not expand the core v1.0 published boundary.
Read this page as a Website summary of a profile reference scenario, then defer to the upstream repo asset and Docs reference for the governed detail.