Extension Module
Enables capability injection, policy enforcement, and integrations through a standardized extension mechanism.
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 Extension module defines where protocol semantics end.
It declares the boundary for custom behavior — allowing implementations to extend MPLP without violating core invariants.
Extension is a boundary declaration, not a plugin system.
Architecture
Interaction Model
Dependencies and event emissions.
Scope
- Extension MAY attach metadata to other artifacts.
- Extension MUST NOT violate core protocol invariants.
Observability
- Extension events SHOULD be traceable.
- Non-conformant extensions invalidate conformance claims.
Compliance
Key Constraints
Essential requirements for this module.
- Extensions MUST NOT override normative constraints.
- Core protocol behavior MUST remain deterministic.
- Non-conformant extensions invalidate conformance claims.
Specification
Canonical Schema
The normative JSON structure for this module.
{
"required": [
"meta",
"extension_id",
"context_id",
"name",
"extension_type",
"version",
"status"
],
"optional": [
"config",
"trace",
"events",
"governance"
],
"types": [
"capability",
"policy",
"integration",
"transformation",
"validation",
"other"
]
}Behavior
Lifecycle
Valid states and transitions.
Status Enum
Quick Links
Evaluation Path
Governance → Compliance → Golden Flows → Adoption Signals