Introduction to MPLP
Welcome to the Multi-Agent Lifecycle Protocol (MPLP) documentation. This section provides foundational context for understanding the protocol's purpose, scope, and design philosophy.
[!NOTE] Orientation Only
Introduction pages help readers enter the docs set, but they do not replace schema-backed specification pages, repository truth sources, or the scoped authority model described in Entry Points.
What is MPLP?
MPLP is a vendor-neutral, schema-first protocol for representing lifecycle artifacts and constraints in agent workflows.
Its formal baseline is anchored in repository-backed schemas, invariants, and approved governance records. This introduction explains the reading path into that baseline; it does not create an independent doctrine layer.
MPLP is not a runtime, framework, or product. It is a normative specification that enables interoperability across diverse agent implementations.
Canonical-First Reading Path
| Document | Purpose |
|---|---|
| Entry Points | Authority boundary and public-surface responsibilities |
| Specification | Formal reading path into modules, profiles, observability, and architecture |
| Protocol Overview | Bounded orientation to the protocol reading order |
| Evaluation & Governance | Conformance, evidence, and Validation Lab reference surfaces |
| Guides | Runtime, SDK, and example guidance after the spec/reference baseline is clear |
| Docs Map | Navigation guide for the documentation |
| Glossary | Navigation glossary pointing to canonical pages |
| API Quick Reference | Schema and endpoint summary |
| POSIX Analogy | Conceptual analogy only |
Canonical Distinctions
The introduction pages reassert these distinctions:
- Protocol vs runtime: protocol semantics are defined in formal sources; runtimes realize those semantics.
- Protocol vs product: MPLP is not a framework, product, or hosted system.
- Specification/reference vs guides: specification/reference establishes the baseline; guides follow it.
- Repository vs projection surfaces: repository truth source first, documentation projection second, website positioning third, Validation Lab adjudication separate.
What This Section Contains
| Document | Purpose |
|---|---|
| Protocol Overview | High-level orientation without restating the full spec |
| Docs Map | Navigation guide for the documentation |
| API Quick Reference | Schema and endpoint summary |
| Glossary | Reading aid for key terms and where to read them first |
| POSIX Analogy | Conceptual mapping to familiar OS concepts |
Getting Started
- Start with Entry Points for surface roles and authority boundaries.
- Move next to Specification for the canonical reading path into formal docs surfaces.
- Use Protocol Overview only as an orientation bridge.
- Use Examples only after the specification/reference baseline is clear.
MPLP = Multi-Agent Lifecycle Protocol (not a license, not a product)