MSP-1 schema

compliance

Deprecated compatibility schema for legacy MSP-1 compliance declarations. New MSP-1 v1.0.2 declarations should omit this term.

MSP-1 v1.0.2 • Status: Deprecated compatibility • Last updated 2026-06-29

compliance schema definition

Machine-readable compatibility structure for recognizing legacy compliance declarations without treating them as active MSP-1 v1.0.2 metadata.

compliance schema JSON


## Status: change Normative → Deprecated.
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://msp-1.org/schema/compliance/compliance.json",
  "title": "MSP-1 Compliance Schema",
  "description": "Deprecated compatibility schema for legacy MSP-1 compliance declarations. New MSP-1 v1.0.1 declarations should omit compliance.",
  "$comment": "MSP-1 v1.0.2 sunsets compliance as deprecated compatibility only. Do not emit compliance in new declarations. Validators should issue a soft advisory warning when compliance is encountered and may parse existing compliance declarations only for backward compatibility or migration assistance. compliance should not be treated as proof of correctness, trust, authority, validation, implementation quality, or protocol conformance.",
  "deprecated": true,
  "type": "object",
  "properties": {
    "standard": {
      "type": "string",
      "description": "Legacy name or identifier of the standard or profile being referenced."
    },
    "version": {
      "type": "string",
      "description": "Legacy version of the referenced standard or profile."
    },
    "level": {
      "type": "string",
      "enum": [
        "partial",
        "core",
        "extended",
        "authoritative"
      ],
      "description": "Legacy declared compliance level."
    },
    "scope": {
      "type": "string",
      "description": "Legacy description of what the compliance statement applied to."
    },
    "status": {
      "type": "string",
      "enum": [
        "in-progress",
        "active",
        "deprecated"
      ],
      "description": "Legacy lifecycle status of the compliance statement."
    },
    "lastReviewed": {
      "type": "string",
      "format": "date",
      "description": "Legacy date when the compliance declaration was reviewed or updated."
    },
    "reviewedBy": {
      "type": "string",
      "description": "Legacy identifier or URL for the entity that last reviewed or confirmed compliance."
    },
    "evidence": {
      "type": "array",
      "description": "Legacy list of URLs or identifiers pointing to evidence of compliance.",
      "items": {
        "type": "string"
      }
    },
    "notes": {
      "type": "string",
      "description": "Legacy free-form notes about the compliance claim, caveats, or implementation details."
    },
    "verification": {
      "type": "object",
      "description": "Legacy verification metadata attached to the compliance declaration.",
      "properties": {
        "level": {
          "type": "string",
          "enum": [
            "self-declared",
            "verified",
            "authoritative"
          ],
          "description": "Legacy verification level applied to this compliance statement."
        },
        "verifiedBy": {
          "type": "string",
          "description": "Legacy URL or identifier of the verifying entity."
        }
      },
      "additionalProperties": false
    },
    "core": {
      "type": "boolean",
      "deprecated": true,
      "description": "Deprecated legacy boolean compatibility field. Do not use in new MSP-1 v1.0.1 declarations."
    },
    "verified": {
      "type": "boolean",
      "deprecated": true,
      "description": "Deprecated legacy boolean compatibility field. Do not use in new MSP-1 v1.0.1 declarations."
    },
    "authoritative": {
      "type": "boolean",
      "deprecated": true,
      "description": "Deprecated legacy boolean compatibility field. Do not use in new MSP-1 v1.0.1 declarations."
    },
    "versionRange": {
      "type": "string",
      "deprecated": true,
      "description": "Deprecated legacy version-range compatibility field. Do not use in new MSP-1 v1.0.1 declarations."
    },
    "validatedAt": {
      "type": "string",
      "deprecated": true,
      "description": "Deprecated legacy validation timestamp compatibility field. Do not use in new MSP-1 v1.0.1 declarations."
    },
    "validatedBy": {
      "type": "string",
      "deprecated": true,
      "description": "Deprecated legacy validator identifier compatibility field. Do not use in new MSP-1 v1.0.1 declarations."
    }
  },
  "additionalProperties": false,
  "examples": [
    {
      "standard": "MSP-1 core",
      "version": "1.0.2",
      "level": "core",
      "scope": "documentation only",
      "status": "deprecated"
    },
    {
      "core": true,
      "verified": true,
      "authoritative": false,
      "versionRange": "MSP-1.0.x"
    }
  ]
}


 

Schema notes

compliance is sunset in MSP-1 v1.0.2 and should not be emitted in new declarations.

Legacy compliance declarations may be parsed for backward compatibility, migration assistance, or advisory validator output. They should not be treated as proof of correctness, trust, authority, validation, implementation quality, or protocol conformance.