Definition

msp:compliance was formerly used to describe declared implementation or standards-conformance status. In MSP-1 v1.0.1, this term is sunset and preserved only so validators, agents, and migration tools can recognize legacy declarations.

New MSP-1 v1.0.2 metadata should not include compliance. Useful meaning formerly placed in compliance should be routed to active MSP-1 terms or validator/tooling output as appropriate.

Deprecated usage

Legacy level-based compliance declarations may be parsed for compatibility or migration assistance.

{
  "msp:compliance": {
    "standard": "MSP-1 core",
    "version": "1.0.0",
    "level": "core",
    "scope": "documentation only",
    "status": "deprecated"
  }
}

Earlier boolean-style examples are also deprecated compatibility syntax and should not be emitted in new declarations.

{
  "msp:compliance": {
    "core": true,
    "verified": true,
    "authoritative": false,
    "versionRange": "MSP-1.0.x"
  }
}

Preferred v1.0.1 pattern

New MSP-1 v1.0.1 declarations should omit compliance and express active meanings through the relevant terms.

{
  "msp:protocol": {
    "name": "MSP-1",
    "version": "1.0.1"
  },
  "msp:discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  }
}

Guidance

• New MSP-1 v1.0.1-v1.0.2 declarations should not include compliance.
• Legacy compliance declarations may be ignored or surfaced as advisory compatibility information.
• The presence of compliance should not by itself invalidate an otherwise interpretable MSP-1 declaration.
• Compliance should not be treated as proof of correctness, trust, authority, validation, implementation quality, or conformance.
• Where a legacy compliance declaration expresses useful meaning, migrate that meaning to active terms or external validator output rather than preserving compliance.

Related Terms