Core Module
Serves as the MPLP protocol manifest. Declares protocol version, enabled modules, and runtime state configuration.
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
Purpose & Scope
What this module exists for.
Core defines protocol metadata and structural glue, not execution semantics.
It exists for:
- Consistency: Unified version and profile declarations.
- Parsability: Machine-readable protocol manifest.
- Identity: Stable module references across implementations.
Boundary
Non-Goals
What this module is NOT.
Core is NOT:
- A runtime or orchestration layer.
- An execution controller.
- A decision-making module.
If you need to "do something", Core is the wrong module.
Specification
Canonical Schema
The normative JSON structure for this module.
{
"required": [
"meta",
"core_id",
"protocol_version",
"status",
"modules"
],
"optional": [
"trace",
"events",
"governance"
],
"moduleDescriptor": {
"required": [
"module_id",
"version",
"status"
],
"statusEnum": [
"enabled",
"disabled",
"experimental",
"deprecated"
]
}
}Behavior
Lifecycle
Valid states and transitions.
Status Enum
Quick Links
Evaluation Path
Governance → Compliance → Golden Flows → Adoption Signals