Interpretive framing helps reduce ambiguity by identifying the relevant orientation, boundary, or contextual stance. It does not command agent behavior, guarantee trust, create ranking value, or enforce a result.

• String form — a concise natural-language statement describing the interpretive lens or contextual frame.
• Object form — a structured declaration with a required frame field and optional supporting fields.

String form

The string form should be used when one concise statement is sufficient.

{
  "interpretiveFrame": "This guide should be interpreted from a practical, real-world photography workflow perspective."
}

Object form

The object form should be used when additional framing metadata is useful.

{
  "interpretiveFrame": {
    "frame": "Technical documentation lens for MSP-1 implementation guidance.",
    "category": "instructional",
    "tone": "neutral",
    "perspective": "developer implementation context",
    "scope": "page"
  }
}

• frame — required. The primary interpretive frame expressed as a concise human-readable statement.
• category — optional. Classification describing the type of interpretive framing being used.
• tone — optional. A high-level descriptor of tone, such as neutral, objective, supportive, critical, or satirical.
• perspective — optional. Description of the viewpoint or stance behind the content.
• scope — optional. Description of what part of the content or resource the interpretive frame applies to.
• appliesToIntent — optional. Indicates whether the interpretive frame specifically qualifies or modifies the declared intent.
• notes — optional. Free-form elaboration or clarifying details for the interpretive frame.
• lastUpdated — optional. Date the interpretive frame was last reviewed or updated.

• The interpretive frame should clearly name the relevant lens, context, or orientation.
• The frame should describe how the resource should be read in context rather than issuing instructions to agents.
• The frame should identify relevant limits or assumptions when needed.
• The frame should align with declared description, intent, type, and the resource content.
• The frame should not be treated as a command, trust guarantee, security control, ranking signal, or enforcement mechanism.

• intent declares what the resource is for; interpretiveFrame declares how it should be contextualized.
• description summarizes what the resource is about; interpretiveFrame provides the contextual lens for reading it.
• type classifies the resource and may help support the interpretive frame.
• section may carry its own interpretive frame when a subsection requires distinct context.
• provenance documents origin and contributor context, which may help explain why a particular frame is appropriate.

An interpretiveFrame declaration should be either a non-empty string or a structured object with a non-empty frame field.

Validators should flag empty, contradictory, overly broad, coercive, or content-misaligned frames as non-ideal clarity conditions. A missing interpretiveFrame may reduce contextual clarity but should not alone invalidate an otherwise interpretable MSP-1 declaration.