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",
  "@type": "MSPSite",
  "protocol": {
    "name": "MSP-1",
    "version": "1.0.1"
  },
  "discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  },
  "site": {
    "id": "example-site",
    "name": "Example Domain",
    "url": "https://example.com/",
    "description": "A reserved example domain used for documentation examples.",
    "intent": "Provide a publicly accessible example domain for documentation and illustrative use.",
    "canonical": {
      "url": "https://example.com/"
    },
    "interpretiveFrame": {
      "frame": "The site should be interpreted as a reserved documentation example domain, not as an operational service, trust guarantee, ranking guarantee, legal claim, security mechanism, validation guarantee, or enforcement mechanism.",
      "category": "informational",
      "scope": "site"
    }
  },
  "provenance": {
    "type": "ai-assisted",
    "source": "https://example.com/",
    "timestamp": "2026-07-03T00:00:00-04:00",
    "notes": "MSP-1 site declaration generated from the explicitly supplied homepage URL and accessible page content; human review recommended."
  },
  "revision": {
    "id": "msp-site-rev-2026-07-03",
    "revisionDate": "2026-07-03",
    "revisionNotes": "Initial MSP-1 v1.0.1 site declaration generated from the supplied homepage URL and accessible page content; human review recommended.",
    "revisionVersion": "1.0.1"
  }
}

Page-Level Declaration

{
  "@context": "https://msp-1.org/schema/msp-1-page.json",
  "@type": "MSPPage",
  "protocol": {
    "name": "MSP-1",
    "version": "1.0.1"
  },
  "discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  },
  "page": {
    "id": "example-homepage",
    "url": "https://example.com/",
    "title": "Example Domain",
    "name": "Example Domain",
    "description": "A simple example domain page intended for documentation examples.",
    "type": "example-homepage",
    "canonical": {
      "url": "https://example.com/"
    },
    "intent": {
      "statement": "Provide a reserved domain page for documentation examples without requiring permission.",
      "category": "informational",
      "scope": "page"
    },
    "interpretiveFrame": {
      "frame": "Content should be interpreted as a documentation example resource, not as an operational service, trust guarantee, ranking guarantee, legal claim, security mechanism, validation guarantee, or enforcement mechanism.",
      "category": "informational",
      "scope": "page"
    }
  },
  "provenance": {
    "type": "ai-assisted",
    "source": "https://example.com/",
    "timestamp": "2026-07-03T00:00:00-04:00",
    "notes": "MSP-1 homepage declaration generated from the explicitly supplied URL and accessible page content; human review recommended."
  },
  "revision": {
    "id": "msp-page-rev-2026-07-03",
    "revisionDate": "2026-07-03",
    "revisionNotes": "Initial MSP-1 v1.0.1 homepage declaration generated from the supplied URL and accessible page content; human review recommended.",
    "revisionVersion": "1.0.1"
  }
}
  

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.