View schema JSON
The formal JSON schema defining the expected structure and fields for the MSP-1 trust term.
AI-friendly semantics for trusted information.
MSP-1 schema
Declares trust-related context, confidence indicators, verification information, and supporting signals associated with an MSP-1 resource.
Machine-readable structure for declaring trust-context metadata using a lean object form.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://msp-1.org/schema/trust/trust.json",
"title": "MSP-1 Trust Schema",
"description": "Schema for declaring trust-related context, confidence indicators, verification information, and supporting signals associated with an MSP-1 resource.",
"$comment": "MSP-1 v1.0.1 uses object form as canonical for trust. level is required and uses low, medium, or high. verificationLevel is separate from level and uses self-declared or verified. Authority meaning belongs in the authority term; legacy authoritative trust values should receive advisory compatibility handling. Trust is declarative context and does not itself establish correctness, authority, safety, verification, compliance, or ranking priority.",
"type": "object",
"properties": {
"level": {
"type": "string",
"enum": [
"low",
"medium",
"high"
],
"description": "General declared confidence context for the resource. This value is publisher-declared and should be evaluated alongside provenance, reviewer, authority, revision, and observable content."
},
"verified": {
"type": "boolean",
"description": "Indicates whether the resource has undergone a declared verification process."
},
"verificationLevel": {
"type": "string",
"enum": [
"self-declared",
"verified"
],
"description": "Declared verification status associated with the resource. Verification context should not be treated as proof of correctness, authority, ranking priority, or trust by itself."
},
"verifiedBy": {
"type": "string",
"description": "Identifier for the person, organization, or system that performed or declared verification."
},
"verificationDate": {
"type": "string",
"format": "date",
"description": "Date when verification was performed or declared."
},
"confidence": {
"type": "string",
"enum": [
"low",
"medium",
"high"
],
"description": "Declared confidence in the accuracy, reliability, or interpretive stability of the resource."
},
"signals": {
"type": "array",
"description": "Optional list of trust-related supporting signals or justifications.",
"items": {
"type": "string"
}
},
"auditTrail": {
"type": "array",
"description": "Optional chronological audit entries describing trust or verification events.",
"items": {
"type": "object",
"properties": {
"event": {
"type": "string",
"description": "Trust or verification event label."
},
"performedBy": {
"type": "string",
"description": "Identifier for the person, organization, or system associated with the event."
},
"date": {
"type": "string",
"format": "date",
"description": "Date of the trust or verification event."
},
"notes": {
"type": "string",
"description": "Optional notes for the audit entry."
}
},
"required": [
"event"
],
"additionalProperties": false
}
},
"notes": {
"type": "string",
"description": "Optional notes describing trust context, limits, caveats, or interpretation."
}
},
"required": [
"level"
],
"additionalProperties": false
} The formal JSON schema defining the expected structure and fields for the MSP-1 trust term.
See the corresponding namespace term for conceptual usage, examples, and related MSP-1 terms.
The canonical MSP-1 v1.0.2 form for trust is an object with level as the required field.
The active level values are low, medium, and high. Verification status is expressed separately through verified, verificationLevel, verifiedBy, and verificationDate. Trust metadata is declarative context and should not be treated as proof of correctness, authority, safety, verification, or ranking priority by itself.