Non-Certification & Non-Endorsement NoticeThis page provides an informational overview of the MPLP conformance model. It does not constitute certification, endorsement, or official verification.For formal definitions, see docs.mplp.io.

Standards

Conformance Model

The MPLP specification describes a three-level conformance model covering Schema (L1), Governance (L2), and Behavioral (L3) interoperability. See docs for formal requirements.

The following is an informational summary of the conformance model. For formal requirements, see docs.mplp.io.

Schema

Data Interoperability

→Schema alignment with JSON Schema definitions
→Coverage of the 10 protocol modules
→Identifier and invariant consistency

Governance

Policy Interoperability

→Confirm semantics for gated actions
→Role and permission boundary patterns
→Governance signal emission patterns

Behavioral

Runtime Interoperability

→Golden Flows 01–05 as verification scenarios
→Structured, replayable execution traces
→Drift detection and recovery patterns

Verification

Explore Verification Evidence

The documentation describes Golden Flows as protocol-level verification scenarios for assessing conformance. Evidence generation and evaluation are described in the docs.

Explore in Documentation View Golden Flows

Related Positioning: Agentic State Sovereignty · Semantic Drift Control

Conformance Checklist (v1.0)Golden Flows Enterprise Evaluation Schemas Registry Agent OS Protocol Governed Stack Evidence Chain

Canonical References

Definition →Normative Spec (Docs) →Source of Truth (Repo) →

This website provides discovery and positioning content only. Normative requirements live in Docs; the ultimate source of truth is the Repository.

Next Steps

Read the Spec →View Source of Truth →See Verification Evidence →

Evidence is evaluated through documentation-defined scenarios and replayable artifacts. This website does not certify or endorse implementations.