Document Type: Informative
This document is informative only. It does not define protocol requirements.
Documentation Overview
The Repository is the authoritative truth source for MPLP protocol definitions, schema definitions, invariant definitions, and frozen governance records.
This documentation site is the official specification/reference projection surface. It explains and projects repository truth, but it does not create a second source of protocol authority.
The Website handles discovery and positioning. The Validation Lab handles evidence adjudication. Neither surface overrides repository truth for protocol meaning.
If an overview page on docs conflicts with repository-backed schemas, invariants, or approved constitutional records, the repository-backed sources prevail. See Entry Points for the scoped authority model.
Purpose of This Documentation
This documentation site serves as a technical reference for implementers of the MPLP (Multi-Agent Lifecycle Protocol).
It explains:
- how the protocol is structured,
- how protocol concepts map to implementation-oriented artifacts,
- how protocol behavior can be verified through self-declared conformance and evidence.
This documentation does not prescribe implementation strategies or operational architectures.
Canonical Reading Order
Use the documentation in this order:
- Entry Points Read the authoritative surface split first: repository truth source, documentation projection, website positioning, Validation Lab adjudication.
- Introduction Use introduction pages for orientation only. They do not replace the formal specification sections.
- Specification Read the specification section indexes first, then the linked schema-backed module, profile, and observability pages.
- Evaluation Read evaluation surfaces after the specification baseline is clear.
- Guides Use runtime, SDK, and example guides only after the specification/reference baseline is clear.
Current Baseline
This documentation set is aligned to the frozen MPLP protocol_version: 1.0.0
line.
Formal protocol meaning remains anchored in repository-backed schemas, invariants, and approved governance records. Introductory and navigational pages on docs exist to route readers to those sources, not to compete with them.
Explicit Non-Goals and Limitations
This site is not:
- a product website,
- a marketing or promotional surface,
- a certification, endorsement, or compliance authority.
This documentation does not guarantee:
- feature completeness across all implementations,
- runtime behavior parity between SDKs, runtimes, or products,
- enterprise deployment outcomes or operational readiness.
MPLP specifies lifecycle invariants and evidence structures.
Implementation choices, optimization strategies, and operational characteristics remain explicitly out of scope.
For discovery and positioning, refer to the MPLP website at https://www.mplp.io.