Inputs
- Network intent and change proposals
- Certificates and trust material
- Topology, flow and stability signals
Extended platform
MZiNG Network
Network change assurance inside the Control Plane.
In-process Control Plane network change and commit assurance: topology, network gates, potential, routing and containment plan surfaces. Not packet-level enforcement.
Responsibility
What MZiNG Network is responsible for
MZiNG Network is the network-facing change and commit assurance capability inside the Control Plane. It exposes network admission, certificates, topology, gates, potential and routing surfaces so network change can be admitted and planned through the same commit-invariant model. It is not a separate network coordination service.
Network change has a different blast radius and a different evidence trail. MZiNG Network provides the Control Plane's network change surfaces: network intents, certificate handling, topology and gate evaluation, potential and routing plans, stability and flow telemetry.
The honest boundary is enforcement and coordination. The reviewed implementation operates at plan boundaries inside a single-writer Control Plane; it does not apply policy to packets on a device, coordinate multiple nodes, or arbitrate with a configured arbiter.
Lifecycle position
Where it sits in the governance lifecycle
Stage numbering is canonical across the site. Open the interactive lifecycle to see every component with responsibilities at each stage.
Admission
Establish authority independently of the executor.
Evidence and audit
Keep linked, ordered, reviewable records.
Verified capabilities
What is verified today
Capabilities are drawn from the product register. Each one is bounded by the limitations stated further down this page.
- Network admission and permit handling
- Certificate and trust material surfaces
- Topology, gate, potential and routing plan surfaces
- Stability, flow and telemetry read surfaces
- Containment planning for abnormal network behaviour
Outputs
- Network admission decisions
- Routing and containment plans
- Telemetry and health records
Evidence and maturity
What the evidence supports
Maturity describes verified engineering evidence in a bounded environment. It is not a production-readiness statement.
Maturity note
Network change/commit assurance and read surfaces are implemented with Go tests and prior smoke evidence, and network routes were exercised during the RC audit. There is no packet-level or device enforcement, no multi-node coordination, and the reviewed configuration has no arbiter configured.
Not production-qualified
This label describes verified engineering evidence only. No production deployment, certification, benchmark or customer outcome is claimed.
Evidence recorded
- Control Plane MZiNG network readiness record and `/v1/network/*` surfaces.
- MZiNG Network implementation report v4 and snapshot.
- Capability audit 2026-11-03: network read routes exercised; enforcement plan-level only.
- Integration matrix row 15: packet-level enforcement not implemented.
Dependencies
- MZiNG
- Control Plane
- Gatekeeper
Dependencies are stated as the product register records them. A dependency is not automatically production-qualified; see its own product or component page for its maturity and limitations.
Limitations
What this product does not do (yet).
Limitations are stated before the evaluation questions so they cannot be missed, downplayed or treated as future-work footnotes.
Limitations — read before evaluating
- Not a network coordination service: no multi-node or multi-cluster coordination, single-writer store, arbiter not configured.
- Packet-level and device-level enforcement is not implemented; plans are applied at file/HTTP boundaries.
- No real device apply or read-back was available in the reviewed environment.
- Prior smoke evidence was not re-run against the current head.
No capability on this page should be read as production qualification. If a limitation is material to your use case, it belongs in the evaluation scope — not after it.
Relationship to the platform
How it fits
MZiNG Network is the network-specialised extension of MZiNG change assurance, sharing the same admission, evidence and containment model.
Evaluation questions
- Which network changes would be admitted through this path?
- Where does enforcement actually apply today?
- What evidence would a network reviewer need?
Next step
Evaluate MZiNG Network against a real control problem.
Bring a system boundary, an action class and a failure mode. The first step is to agree what should be governed and what evidence would count.