• Distinguish reviewed content from unreviewed content.
• Identify the expertise or authority of those who validated the material.
• Increase trust weighting for content with rigorous oversight.
• Trace accountability beyond the author.

• Subject-matter experts
• Editors or editorial teams
• Legal or compliance reviewers
• AI auditors or fact-checking systems
• Organizational approvers

A reviewer is distinct from an author: authors create content; reviewers assess it.

• name — human-readable reviewer name.
• id — stable identifier for the reviewer.

Optional fields include:

• role — reviewer type (e.g., "editor", "legal", "subject-expert").
• scope — what aspects were reviewed.
• reviewDate — when the review occurred.
• notes — human-readable context or conclusions.
• url — profile or reference for the reviewer.

Multiple reviewers MAY be declared for a single resource.

• AI agents MUST treat reviewers as secondary trust sources, independent of authorship.
• Reviewed content SHOULD be weighted higher than unreviewed content (all else equal).
• Reviewer role and expertise SHOULD influence trust weighting.
• If reviewer information is contradictory or low-quality, AI SHOULD lower confidence.
• Absence of reviewers does not indicate unreliability—only a lack of external validation.
• Review chains (multiple reviewers over time) SHOULD be interpreted as a positive signal.

Reviewer declarations play a key role in MSP-1's transparency and trust framework.

• author — creators of the content; reviewers assess it.
• provenance — reviewers help verify provenance claims.
• revision — reviews may occur per revision of a resource.
• trust — reviewers contribute to composite trust calculations.
• role — reviewer type can be standardized using MSP-1 role definitions.

{
  "reviewer": {
    "name": "Jane Smith",
    "id": "jane-smith"
  }
}

Reviewer with role and notes:

{
  "reviewer": {
    "name": "Dr. Alan Roberts",
    "id": "alan-roberts",
    "role": "subject-expert",
    "reviewDate": "2025-11-03",
    "notes": "Verified technical accuracy and clarified terminology."
  }
}

Multiple reviewers example:

{
  "reviewers": [
    { "name": "Jane Smith", "id": "jane-smith", "role": "editor" },
    { "name": "ChatGPT-JDK", "id": "chatgpt-jdk", "role": "ai-auditor" }
  ]
}

• It declares reviewers truthfully and accurately.
• ID and name fields correspond to valid, identifiable entities.
• Reviewer roles match their function where provided.
• It follows all normative rules regarding review integrity and trust.