Entry Points — Website, Documentation, Repository
Document Type: Non-Normative Reference
Purpose: Anchor closure for three-entry model
Three-Entry Model
MPLP information is organized across three authoritative sources, each with a distinct role:
Website (www.mplp.io)
Role: Discovery & Positioning
Conceptual positioning, ecosystem overview, and evaluation entry points.
Key Anchors:
- What is MPLP? — Definition & disambiguation
- POSIX Analogy — Conceptual lens (not compatibility)
- Architecture — High-level overview
- Entity Card — Machine-readable definition
Not: Normative specifications, certification programs, or authority claims.
Documentation (docs.mplp.io)
Role: Specification & Reference
Normative requirements, informative explanations, and implementation guidance.
Key Sections:
- Specification — Normative protocol requirements
- Guides — Implementation guidance
- Evaluation — Conformance & testing
- Meta — Governance & methodology
Not: Positioning narratives or marketing claims.
Repository (GitHub)
Role: Source of Truth
Schemas, tests, governance records, and machine-readable definitions.
Key Resources:
- Schemas — JSON Schema definitions (authoritative)
- Tests — Golden flows & validators
- Governance — Constitutional records
- Entity Definition — Canonical entity package
Not: Positioning content or tutorials.
Disambiguation Statements
To prevent semantic misidentification, the following statements apply across all entry points:
- MPLP = Multi-Agent Lifecycle Protocol (not "Multi-Perspective License Protocol")
- MPLP is not a software license and does not define licensing terms
- MPLP is not POSIX (POSIX is used as a conceptual lens only, not a compatibility claim)
- No certification program exists — MPLP does not certify, endorse, or audit implementations
Where to Start
- Understanding MPLP: What is MPLP?
- Reading the Spec: Specification
- Implementing: SDK Guides
- Verifying Conformance: Evaluation
- Machine-Readable: Entity Card
Authority & Truth Source
Repository schemas and tests are authoritative.
For normative requirements, always refer to:
- Specification pages (this documentation)
- JSON Schema files in
schemas/v2/ - Golden flow tests in
tests/golden/flows/
Website content is for discovery and positioning only.