MSP-1 Implementation Guide

Who This Guide Is For

This guide is intended for teams evaluating or implementing MSP-1 in practical environments.

• Enterprise teams evaluating MSP-1 across content systems and AI workflows.
• Agencies delivering human-reviewed MSP-1 implementations for clients.
• Developers integrating MSP-1 into CMS, pipelines, and tooling.

Overview

MSP-1 is a declarative semantic layer that helps AI systems interpret content with greater clarity. It is additive, non-visual, and integrates with existing systems.

Core Components

• Site-level declaration
• Page-level declaration
• Validation
• Human review

Implementation Path

1. Select pilot content
2. Create site-level MSP-1
3. Add page-level declarations
4. Review key fields
5. Validate
6. Deploy and expand

Site-Level Declaration

{
  "@context": "https://msp-1.org/schema/msp-1-site.json",
  "protocol": {
    "name": "MSP-1",
    "version": "1.0.0"
  },
  "discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  },
  "site": {
    "id": "https://example.com/#site",
    "name": "Example Domain",
    "url": "https://example.com",
    "description": "A placeholder domain used for illustrative purposes in documentation and technical examples.",
    "intent": "To serve as a canonical example domain for use in documentation, testing, and protocol demonstrations.",
    "protocol": "MSP-1",
    "version": "1.0.0"
  },
  "authority": {
    "subjectId": "https://example.com/#site",
    "scope": "site",
    "level": "self-asserted"
  },
  "provenance": {
    "type": "ai-assisted",
    "confidence": "medium",
    "method": "ai-generated"
  },
  "compliance": {
    "core": true
  },
  "trust": {
    "level": "self-asserted",
    "scope": "site"
  },
  "revision": {
    "id": "site-rev-1",
    "revisionDate": "2026-05-02T00:00:00Z",
    "revisionNotes": "Initial MSP-1 site-level declaration for example.com. Generated as a reference example — human review recommended before production use.",
    "revisionVersion": "1.0.0"
  },
  "generatedAt": "2026-05-02T00:00:00Z"
}

Page-Level Declaration

{
  "@context": "https://msp-1.org/schema/msp-1-page.json",
  "@type": "MSPPage",
  "protocol": {
    "name": "MSP-1",
    "version": "1.0.0"
  },
  "discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  },
  "page": {
    "id": "https://example.com/",
    "url": "https://example.com/",
    "canonical": "https://example.com/",
    "title": "Example Domain",
    "name": {
      "short": "Example Domain"
    },
    "description": {
      "short": "A placeholder domain used for illustrative purposes in documentation and technical examples."
    },
    "intent": {
      "statement": "To demonstrate a minimal, valid MSP-1 page-level declaration for documentation and protocol testing purposes.",
      "category": "informational",
      "scope": "page"
    },
    "interpretiveFrame": {
      "frame": "This page is a static illustrative example, not a commercial or editorial resource.",
      "category": "informational",
      "scope": "page"
    }
  },
  "author": {
    "name": "IANA",
    "type": "Organization",
    "id": "https://example.com/#author"
  },
  "provenance": {
    "type": "ai-assisted",
    "confidence": "medium",
    "method": "ai-generated"
  },
  "canonical": {
    "url": "https://example.com/",
    "reason": "Declared preferred URL for this page."
  },
  "trust": {
    "level": "self-asserted",
    "scope": "page"
  },
  "revision": {
    "id": "rev-1",
    "revisionDate": "2026-05-02T00:00:00Z",
    "revisionNotes": "Initial MSP-1 page-level declaration for example.com homepage. Generated as a reference example — human review recommended before production use.",
    "revisionVersion": "1.0.0"
  },
  "generatedAt": "2026-05-02T00:00:00Z"
}
  

Validation

• Structural validation (schema + JSON)
• Semantic validation (truth vs content)

Human Review

Automated generation is possible, but human validation ensures accuracy, especially for intent, authority, and trust.

Integration Patterns

• CMS templates
• Build pipelines
• Documentation systems
• Ecommerce platforms

Governance Considerations

MSP-1 does not introduce tracking or enforcement. It should align with existing compliance and governance processes.

Scaling

Expand only after patterns are validated. Reuse templates and workflows to maintain consistency.

Key Principles

• Declare conservatively
• Match content accurately
• Integrate, don’t replace
• Validate continuously
• Expand progressively

Summary

MSP-1 implementation is straightforward: define, validate, review, and expand. It reduces ambiguity without adding operational complexity.