Skip to main content
⚠️ Draft — Non-authoritative content (noindex)
INFORMATIVEDRAFTDocumentation Governance

Semantic Alignment Overview

This page explains the docs-side alignment posture for MPLP. It does not certify semantic completeness, define new mappings, or replace frozen protocol sources.

1. Alignment Baseline

The repaired docs set now follows a canonical-first reading order:

  1. repository-backed schemas, invariants, profile manifests, and taxonomy files
  2. repaired first-order specification/reference pages
  3. evaluation/reference projections
  4. guides and other downstream explanatory pages

This page exists only to describe that posture.

2. What Semantic Alignment Means Here

For this documentation surface, semantic alignment means:

  • docs pages should not compete with frozen source artifacts for meaning
  • matrix/registry pages should stay subordinate to first-order repaired specification/reference pages
  • evaluation/reference pages should not redefine protocol semantics
  • explanatory pages should clearly yield to frozen source artifacts when there is tension

3. What This Page Does Not Claim

This page does not claim:

  • that all mappings are canonically defined in docs
  • that docs matrices prove coverage
  • that docs has established runtime validation status
  • that evaluation-reference surfaces are identical to Validation Lab adjudication outputs
  • that a docs-side “semantic system” exists independently of frozen sources

4. Reliable Source Order

When reading or interpreting MPLP docs, use this order:

PrioritySource Type
1Frozen schemas, invariants, profile manifests, taxonomy files
2Repaired first-order module/profile/observability/specification pages
3Repaired validation-lab reference projections and related evaluation entry pages
4Docs-side registries, matrices, and coverage pages

6. References


Final Boundary: this page describes the docs-side alignment posture only. It does not itself create mapping authority or coverage authority.