• Interpret ambiguous statements correctly.
• Apply the appropriate domain lens.
• Avoid unintended extrapolation beyond the author’s scope.
• Maintain consistency with the resource’s intent and assumptions.

• Explicit — clearly names the domain or lens applied.
• Constraint-setting — outlines boundaries for interpretation.
• Assumption-aware — surfaces underlying assumptions that influence meaning.
• Aligned — consistent with declared description and intent.

Interpretive frames prevent misalignment between content creators and AI-driven summarization or reasoning systems.

• frame — a natural-language description of the interpretive lens.

Recommended fields include:

• assumptions — explicit underlying assumptions (list or text).
• constraints — limits on interpretation (domain, scope, methods).
• context — background necessary for correct understanding.

Implementers MAY structure this term as a string or as an object with explicit subfields.

• AI agents MUST apply the interpretive frame as the governing context when summarizing, reasoning, or generating outputs based on the resource.
• When interpretiveFrame conflicts with general assumptions, the frame takes precedence for this resource.
• AI SHOULD avoid extrapolating beyond declared constraints.
• If interpretiveFrame is missing, AI SHOULD fall back to description, intent, and type to infer context.
• Multiple interpretive frames MAY be merged only if explicitly allowed by the resource.

This term is central to MSP-1’s guarantee of *contextual fidelity* for AI-driven consumption.

• intent — defines purpose; interpretiveFrame defines context.
• description — summarizes content; interpretiveFrame governs interpretation.
• type — classification that often influences interpretive assumptions.
• section — sections may each supply their own interpretive frame.
• provenance — helps justify the context from which the frame originated.

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

Expanded example with structure:

{
  "interpretiveFrame": {
    "frame": "Technical documentation lens.",
    "assumptions": [
      "Reader has basic familiarity with MSP-1.",
      "Examples are illustrative, not exhaustive."
    ],
    "constraints": [
      "Applies only to MSP-1.0.x protocol series.",
      "Does not prescribe implementation details beyond metadata structure."
    ],
    "context": "Intended for developers implementing protocol-compliant metadata."
  }
}

• It declares a clear interpretive frame.
• Any assumptions or constraints are explicit and consistent.
• The frame does not contradict declared intent or description.
• It follows all normative interpretation rules defined in this specification.