The Musher document specifications and their JSON Schema 2020-12 bundles. This host serves the schemas and the rendered specifications; the normative Markdown, the conformance suite and the publication ledger live in musher-dev/specifications.
Define a reusable workload and its configuration contract.
Document format: v1 · Latest release: 1.6.1
Read field reference · View examples · JSON Schema · Versions and downloads
Compose components into an application with explicit bindings.
Document format: v1 · Latest release: 1.7.2
Read field reference · View examples · JSON Schema · Versions and downloads
Describe a component or blueprint for the catalog.
Document format: v1 · Latest release: 1.0.1
Read field reference · View examples · JSON Schema · Versions and downloads
Shared rules for document authors and specification implementers.
Document format: v1 · Latest release: 1.1.1
| Family | Current schema URL | Latest release | Downloads | Specification source | Reference |
|---|---|---|---|---|---|
| component | /component/v1/component.schema.json | 1.6.1 | versions.json | spec.md | reference |
| blueprint | /blueprint/v1/blueprint.schema.json | 1.7.2 | versions.json | spec.md | reference |
| listing | /listing/v1/listing.schema.json | 1.0.1 | versions.json | spec.md | reference |
| core | — | 1.1.1 | — | spec.md | specification |
An alias moves within its major version as backward-compatible additions ship.
Automation must pin an exact version instead — those paths are served from verified
immutable release assets, carry an $id naming that exact URL, and never change.
The reference explains each family field by field, beside its specification. It is generated from the bytes each version serves, and is informative — the specification and the bundle are what govern.