Module: collab

Collab Module

Covers broadcast, round-robin, orchestrated, swarm, and pair modes for MAP profile execution.

Status: Frozen

Usage Boundary: This page provides an evaluative summary and a canonical schema excerpt for convenience. The authoritative, versioned specification remains on docs.mplp.io. MPGC does not issue certifications, badges, or endorsements; adoption and conformance are self-assessed by the adopting organization.

Definition

Protocol Role

The normative responsibility of this module.

The Collab module serves as the authoritative coordination contract for multi-agent execution in MPLP.

Its primary role is to define how agents collaborate, independent of:

  • the underlying model implementation,
  • the execution runtime,
  • or the communication transport.

Within the MPLP lifecycle, Collab is responsible for:

  • Declaring who participates in a coordinated activity,
  • Defining how coordination is structured (e.g. broadcast, pair, swarm),
  • Ensuring collaboration semantics remain deterministic, observable, and auditable.

Collab does not perform orchestration itself; it provides the normative coordination rules that orchestration layers MUST follow.

Architecture

Interaction Model

Dependencies and event emissions.

The Collab module operates as a coordination hub and interacts with other MPLP modules as follows:

Dependencies

  • Context: Collab instances MUST reference a valid Context to establish a shared semantic scope.
  • Role: Each participant in a Collab instance MUST be associated with a defined Role.

Emissions & Observability

  • Trace: Collaboration events (e.g. participant join, mode transition) MUST be emitted as traceable protocol events.
  • Confirm / Governance: Certain coordination changes MAY require confirmation or governance enforcement, depending on the execution policy.

Usage in Golden Flows

The Collab module is referenced in the following normative execution patterns:

  • Golden Flow 03 — Multi-Agent Task Coordination
  • Golden Flow 05 — Human-in-the-Loop Collaborative Review

Compliance

Normative Constraints

MUST / SHOULD / MUST NOT requirements.

The following constraints are normative and MUST be enforced by any MPLP-conformant implementation:

  1. A Collab instance MUST reference a valid context_id.
  2. Each participant MUST declare a kind and be associated with a Role.
  3. A Collab instance MUST NOT include participants without explicit identifiers.
  4. The selected coordination mode MUST be one of the protocol-defined modes.
  5. In pair mode, turn ordering MUST be deterministic and reproducible.
  6. Changes to participant sets or coordination mode MUST be traceable.

Failure to meet these constraints results in a non-conformant execution.

Specification

Canonical Schema

The normative JSON structure for this module.

{
  "required": [
    "meta",
    "collab_id",
    "context_id",
    "title",
    "purpose",
    "mode",
    "status",
    "participants",
    "created_at"
  ],
  "optional": [
    "updated_at",
    "trace",
    "events",
    "governance"
  ],
  "participantObject": {
    "required": [
      "participant_id",
      "kind"
    ],
    "kindEnum": [
      "agent",
      "human",
      "system",
      "external"
    ]
  },
  "modes": [
    "broadcast",
    "round_robin",
    "orchestrated",
    "swarm",
    "pair"
  ]
}

Behavior

Lifecycle

Valid states and transitions.

Status Enum

draftactivesuspendedcompletedcancelled

Quick Links

View Full Spec← Back to Modules

Evaluation Path

Governance → Compliance → Golden Flows → Adoption Signals

Enterprise Guide Governance Compliance Golden Flows Adoption