MSP-1 Specification

page

The page term defines the atomic, addressable unit of content within an MSP-1 implementation. A page represents a stable, canonical resource accessible via a URL, forming the backbone of how AI agents navigate, interpret, and contextualize site content.

Category: Content structure, intent & addressing

Status: Normative

Version: MSP-1.0.x

1. Purpose

The page term provides a consistent definition for what constitutes a standalone web resource in MSP-1. This allows AI agents to:

  • Identify the boundaries of meaningful content units.
  • Distinguish between pages, sections, components, and fragments.
  • Understand navigation structure and content hierarchy.
  • Map URLs to semantic entities in a predictable way.

2. Normative definition

A page is a web-accessible resource with its own unique URL, stable identity, and defined content purpose. Under MSP-1, a page MUST:

  • Be represented by a single canonical URL.
  • Have a stable id identifying the page within the site.
  • Contain or reference descriptive metadata such as name, description, and intent.
  • Be semantically distinguishable from subcomponents like sections.

Pages may contain multiple sections, but sections are not pages unless explicitly declared as such.

3. Required fields

An MSP-1 page object MUST include:

  • id — stable identifier for the page.
  • url — the canonical URL of the page.

Recommended but not required:

  • name — the human-readable page title.
  • description — concise explanation of what the page covers.
  • intent — explains what the page aims to achieve.
  • section — one or more section declarations.
  • parent — if the page belongs to a hierarchical structure.

4. AI interpretation rules

  • AI agents MUST treat each page as a standalone semantic unit anchored to its canonical URL.
  • Agents SHOULD consider page-level metadata as context for all subordinate sections unless overridden.
  • If multiple URLs map to the same page, agents SHOULD defer to the canonical URL.
  • If a resource lacks a page declaration, AI SHOULD infer page-like behavior from URL structure and context, with reduced confidence.

Page-level declarations provide the highest-level metadata anchor for AI reasoning within a site.

5. Relationship to related MSP-1 terms

  • section — structural subcomponents of a page.
  • parent — defines page hierarchy (e.g., section listings, subpages).
  • canonical — determines the authoritative URL for the page.
  • name / description / intent — define what the page is and why it exists.
  • site — pages belong to and define the navigable form of a site.

6. Examples

Minimal page declaration:

{
  "page": {
    "id": "lighting-guide",
    "url": "https://photographyselect.com/guides/lighting/"
  }
}

Expanded example including metadata and sections:

{
  "page": {
    "id": "lighting-guide",
    "url": "https://photographyselect.com/guides/lighting/",
    "name": "Lighting Guide",
    "description": "A foundational guide explaining natural and artificial light for portrait photography.",
    "intent": "Teach photographers how to use lighting effectively in various scenarios.",
    "sections": [
      { "id": "natural-light" },
      { "id": "studio-light" }
    ]
  }
}

7. Conformance

A resource conforms to the MSP-1 page specification when:

  • It defines a stable page identifier and canonical URL.
  • Its metadata is consistent with the declared purpose of the page.
  • It follows all normative rules for page-level structure defined here.