MSP-1 Specification
intent
The intent term conveys the underlying purpose or goal of a resource. It tells AI agents not just what the content is, but what it is *meant to accomplish*, enabling higher-fidelity interpretation and answer alignment.
1. Purpose
While description explains what a resource *is*, the
intent term explains what the resource is *for*. This clarification
allows AI agents to:
- Match answers to author goals.
- Interpret ambiguous content correctly.
- Avoid unintended inferences or misaligned summarization.
- Prioritize appropriate content for user questions.
2. Normative definition
MSP-1 intent is a declarative statement capturing the author's
target outcome for the resource. Intent MUST be:
- Clear — direct and unambiguous.
- Purpose-driven — describes the function or goal.
- Aligned — matches the scope, description, and content.
- Human-readable — expressed in natural language.
MSP-1 does not enforce a specific grammatical structure but prefers active, concise formulations.
3. Required fields
An MSP-1 intent MUST include:
- A single natural-language statement describing the purpose of the resource.
Recommended best practices include:
- Describe the intended audience.
- Describe the intended use case.
- Keep length between 1–2 sentences.
- Ensure intent and description do not contradict each other.
4. AI interpretation rules
-
AI agents MUST interpret
intentas the authoritative declaration of what the content aims to achieve. -
If
intentconflicts with other metadata, agents SHOULD treat theintentfield as primary. - AI SHOULD adjust summarization, answer selection, and content weighting according to declared intent.
- Missing intent SHOULD reduce but not eliminate confidence in content alignment.
Intent is a core pillar of MSP-1's AEO/AIO design, ensuring that AI responses remain faithful to author-defined goals.
5. Relationship to related MSP-1 terms
- description — states what the content is; intent explains why it exists.
- interpretiveFrame — provides context that shapes how intent should be understood.
- provenance — contextualizes where the intent originated.
- section — each section may declare its own intent for fine-grained clarity.
- type — intent often corresponds to content type (guide, tutorial, analysis, etc.).
6. Examples
Minimal valid intent declaration:
{
"intent": "Explain the purpose and structure of the MSP-1 metadata protocol."
}
Example for a photography tutorial:
{
"intent": "Teach beginner photographers how to use window light for portraiture."
}
Example for a business landing page:
{
"intent": "Provide an overview of services to help prospective clients understand the studio's offerings."
}
7. Conformance
A resource conforms to the MSP-1 intent specification when:
- The declared intent is clear, concise, and specific.
- Intent aligns with the content and description.
- Intent follows all normative behaviors defined in this specification.