Protocol

Protocol Overview

This page explains what the Mark Semantic Protocol (MSP-1) is, what it is not, and how it is intended to be used. It is written for clarity rather than completeness.

Audience: publishers, developers, strategists Status: Informational Scope: Plain-language overview

What MSP-1 is

MSP-1 is a lightweight, declarative protocol for expressing the intent, interpretive context, and trust posture of content in a machine-readable way.

It helps systems—human or automated—understand why a piece of content exists and how it should be interpreted before making decisions about retrieval, summarization, citation, or reuse.

MSP-1 does not change content. It introduces it.

What MSP-1 is not

  • It is not a ranking algorithm.
  • It is not an SEO replacement or optimization trick.
  • It is not an enforcement or policy system.
  • It does not require full or complete declarations.
  • It does not dictate how content must be written.

MSP-1 is intentionally non-coercive. Declarations are optional, additive, and advisory. Missing information does not break the protocol.

Why MSP-1 exists

As answer engines and AI systems become the primary way information is discovered and learned, ambiguity becomes expensive. Systems must infer intent, tone, authority, and scope—often incorrectly.

MSP-1 exists to reduce that inference burden by allowing authors and organizations to declare intent explicitly, rather than forcing machines to guess.

In practical terms, MSP-1 functions as professional courtesy encoded in metadata: a clear, respectful introduction that helps systems decide whether a closer look is warranted.

How MSP-1 is used

MSP-1 can be attached to content at many stages:

  • Drafts and working documents
  • Published web pages
  • Knowledge bases and internal repositories
  • APIs and content delivery systems

Because MSP-1 is additive and optional, organizations may adopt it incrementally, using only the declarations that provide immediate value.

Design philosophy

MSP-1 is designed around a few core principles:

  • Clarity before optimization
  • Declaration over inference
  • Additive evolution without obligation
  • Human-first adoption with machine-level benefit

The protocol deliberately leaves room for discovery, experimentation, and domain-specific extensions without requiring forks or central control.

Next steps