Definition

msp:discovery declares where MSP-1 metadata is located for deterministic discovery. It allows agents, validators, and implementation tools to locate MSP-1 declarations without guessing alternate filenames or endpoint locations.

The discovery object may appear in site-level declarations, inline MSP-1 metadata blocks, implementation root metadata, or the site’s well-known declaration. It is an additive clarity layer and does not by itself establish correctness, authority, trust, or verification.

Usage

The canonical discovery object uses the fixed root-relative well-known path and a boolean canonical endpoint designation.

{
  "msp:discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  }
}

A site-level MSP-1 declaration may include discovery alongside protocol metadata.

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

Guidance

• Discovery should point to the canonical MSP-1 well-known endpoint.
• wellKnown should use the root-relative path /.well-known/msp.json.
• Consumers and agents should not infer alternate filenames when the canonical endpoint is absent or unreachable.
• The discovery object is an additive clarity layer; older implementations may remain interpretable through the canonical endpoint even when the object is absent.
• discovery.canonical is a boolean endpoint-designation field and should not be interpreted as the separate canonical term.

Related Terms