JPS Core 0.1.0-draft is superseded

This URL held the prose for JPS Core 0.1.0-draft. The current draft is Core 0.2.0-draft.

Nothing here is normative. This page is a signpost. The normative text of a superseded draft is the tagged source, not a rendered page on a mutable site.

Tagged v0.1.0-draft source — the immutable prose as published.
0.1.0-draft release notes — that draft's scope and known limitations.
Core 0.2.0-draft — the current draft. A 0.1.0-draft pack is unchanged in representation and in document-conformance meaning there and needs only its specVersion re-declared; re-declaring it also opts it into that draft's evaluator semantics and confers no conformance on any implementation.
0.2.0-draft release notes — what "preserved" means for the 0.1.0-draft schemas, which stay served at the $id each was published under. Each preserved file matches the tagged artifact in every byte except that $id member, which was re-pointed to this project's domain when the retired pre-publication identifier was withdrawn; the release notes publish the SHA-256 digest of both forms, and the immutable tag remains the authoritative record of its own bytes.
Versioning policy — why a conformance claim is made against one exact version and is never inherited.