MAP Broadcast Fan-out
Multi-Agent Protocol with broadcast. Parallel dispatch to multiple agents.
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-02-broadcast-fanout/README.md. The Docs page is a secondary reference at verified flow reference.
Goal
Validate MAP broadcast mode with parallel agent execution.
Success Criteria
All participants receive broadcast, results aggregated.
Sequence
Execution Steps
Website summary of the scenario sequence represented by this flow.
Broadcast Init
MAP session with broadcast mode.
Multi-Participant
3+ agents registered.
Parallel Dispatch
Task broadcast to all participants.
Result Collection
Responses collected from all agents.
Aggregation
Results merged into final output.
Broadcast Init
MAP session with broadcast mode.
Multi-Participant
3+ agents registered.
Parallel Dispatch
Task broadcast to all participants.
Result Collection
Responses collected from all agents.
Aggregation
Results merged into final output.
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 broadcast for parallel dispatch.
Role Module
All registered participants MUST receive the broadcast.
Plan Module
Results from all participants MUST be aggregated.
Validation
Failure Conditions
This profile-level reference flow should be treated as failed if any of the following conditions occur during evaluation.
Broadcast does not reach all participants.
Parallel execution fails.
Result aggregation is incomplete.
Participant responses are lost.
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.