L2 Coordination & Governance
Scope
This page documents the L2 coordination/profile layer as it is grounded in the frozen MPLP protocol baseline:
- L2 module schemas under
schemas/v2/mplp-*.schema.json - SA and MAP profile manifests under
schemas/v2/profiles/ - SA and MAP invariant sets under
schemas/v2/invariants/
It describes where L2 meaning comes from. It does not introduce additional transition tables, governance models, or runtime algorithms.
Non-Goals
This page does not define:
- physical storage or execution engines
- PSG, VSL, AEL, or other runtime-side abstractions
- additional state machines beyond schema/profile/invariant sources
- orchestrator, committee, hierarchy, or consensus models
- derived approval workflows or reference-runtime behavior
1. Purpose
L2 is the protocol layer where MPLP's object families are coordinated into profile-level constraints.
At this layer:
- module object families are read through their schema-backed specification pages
- profile baselines are read through
sa-profile.yamlandmap-profile.yaml - profile constraints are read through
sa-invariants.yamlandmap-invariants.yaml
This page is a boundary statement over those sources. It is not a replacement for them.
2. Frozen L2 Anchors
2.1 Module Families
L2 coordination meaning is anchored in the schema-backed module pages linked from Modules Overview:
- Context
- Plan
- Confirm
- Trace
- Role
- Dialog
- Collab
- Extension
- Core
- Network
2.2 Profile Baselines
The frozen profile manifests establish the base L2 profile split:
| Profile | Frozen Source | Baseline |
|---|---|---|
| SA | schemas/v2/profiles/sa-profile.yaml | Base single-agent profile |
| MAP | schemas/v2/profiles/map-profile.yaml | Multi-agent profile extending SA |
sa-profile.yaml lists Context, Plan, Trace, Role, and Core as required
modules for the base profile.
map-profile.yaml extends SA and adds Collab, Dialog, and Network.
2.3 Invariant Families
The frozen invariant sets establish the L2 constraint layer:
| File | Constraint Family |
|---|---|
schemas/v2/invariants/sa-invariants.yaml | SA context/plan/trace binding and presence checks |
schemas/v2/invariants/map-invariants.yaml | MAP collab/session structure and participant checks |
This page does not add new invariant IDs or derived invariant meanings beyond those files.
3. What L2 Formally Supports
The frozen sources support these L2-level statements:
- protocol object families may bind to one another through fields such as
context_id,plan_id, and profile-linked references - SA defines the minimal execution profile baseline
- MAP defines the multi-agent profile baseline extending SA
Collab.modeis constrained to the enum declared inschemas/v2/mplp-collab.schema.json- SA and MAP constraints are carried by the invariant files named above
4. What This Page Does Not Create
This page does not create any of the following as protocol requirements:
- new module transition tables
- new terminal-state doctrine
- new participant minimums beyond
map_session_requires_participants - new role UUID rules beyond the frozen invariant files
- orchestrator-required rules
- exclusive-write rules
- conflict-resolution models
- approval-routing doctrine
- reference-runtime execution sequences
If a more specific claim is not present in the frozen module schemas, profile manifests, or invariant files, this page should not be read as creating it.
5. Canonical Reading Path
Read L2 through the linked formal surfaces in this order:
- Modules Overview
- SA Profile
- MAP Profile
- The frozen invariant files referenced above
Use runtime guides only after the L2 baseline is clear.
6. References
schemas/v2/profiles/sa-profile.yamlschemas/v2/profiles/map-profile.yamlschemas/v2/invariants/sa-invariants.yamlschemas/v2/invariants/map-invariants.yaml- Modules Overview
- Profiles Overview
Final Boundary: L2 carries object-family coordination and profile-level constraints only as expressed in the frozen schemas, profile manifests, and invariant files. It does not define new runtime mechanics or derived governance doctrine.