Definition

msp:provenance declares where a resource came from, how it was produced or transformed, and which declared actors or sources contributed to its development.

Provenance describes origin and lineage. It should not be confused with msp:author, msp:reviewer, msp:authority, or msp:trust. Author identifies creation responsibility; reviewer identifies review responsibility; authority and trust are separate interpretive signals.

Usage

Minimal provenance may declare a single origin category.

{
  "msp:provenance": {
    "type": "original"
  }
}

Derived provenance may identify an upstream source when available.

{
  "msp:provenance": {
    "type": "derived",
    "source": "https://example.com/original-article",
    "notes": "Adapted with permission."
  }
}

Multiple provenance categories may be used when the resource has more than one meaningful origin or creation mode.

{
  "msp:provenance": {
    "type": [
      "original",
      "ai-assisted"
    ],
    "contributors": [
      {
        "id": "mark-johnson",
        "role": "author"
      },
      {
        "id": "chatgpt-jdk",
        "role": "ai-partner"
      }
    ],
    "confidence": "high",
    "notes": "Drafted with human guidance and AI structural assistance.",
    "timestamp": "2025-12-11T10:00:00Z"
  }
}

Guidance

• The provenance declaration should accurately reflect the known origin and creation context of the resource.
• The declaration should remain stable unless the resource origin, creation method, or lineage meaningfully changes.
• Derived or aggregated content should identify source material when available.
• Multiple provenance categories may be used when each category is meaningful and non-duplicative.
• Provenance should inform interpretation but should not be treated as proof of authority, correctness, trust, verification, or ranking value by itself.

Related Terms