schepherd¶
Schepherd delivers a chosen JSON Schema from a pinned OCI catalog to a verified local file. Every schema is its own artifact, and the catalog moves between registries without changing its digest. Schemas of your own repository can be declared as local schemas and are used in place. What happens with the file afterwards is decided by your consumer, not by Schepherd.
Start with installation, configuration and the command reference. Read the security and trust model before relying on a pin, publishing if you maintain a schema set, and catalog automation if you operate the weekly catalog update. Versioning explains the two release trains: the client (SemVer) and the schema catalog (time-based revisions).
Schepherd does not validate documents, never contacts upstream schema URLs at runtime and never executes anything that came from a registry. See Architecture for the full list.