Network Module
Defines node collections and connection patterns like hub-spoke and mesh for distributed deployments.
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.
Network defines the boundary where MPLP semantics stop and transport begins.
It declares:
- Existence of communication infrastructure.
- Topology hints (not implementations).
- Node references for distributed deployments.
Boundary
Non-Goals
What this module is NOT.
Network is NOT:
- A communication protocol specification.
- A transport layer definition.
- An API or message format.
MPLP does not dictate how agents communicate — only that they can.
Specification
Canonical Schema
The normative JSON structure for this module.
{
"required": [
"meta",
"network_id",
"context_id",
"name",
"topology_type",
"status"
],
"optional": [
"description",
"nodes",
"trace",
"events",
"governance"
],
"nodeObject": {
"required": [
"node_id",
"kind",
"status"
],
"kindEnum": [
"agent",
"service",
"database",
"queue",
"external",
"other"
]
},
"topologies": [
"single_node",
"hub_spoke",
"mesh",
"hierarchical",
"hybrid",
"other"
]
}Behavior
Lifecycle
Valid states and transitions.
Status Enum
Quick Links
Evaluation Path
Governance → Compliance → Golden Flows → Adoption Signals