v0.3.0

0.3.0, tagged v0.3.0, is the first Core release whose specVersion has no -draft suffix. The released 0.2.0-draft identifier and its tag keep their names. Before the release, one v0.3.0-rc.1 GitHub pre-release gives adopters about a week to verify that their tooling reads the manifest maturity status as draft rather than the retired research-preview value.

Included work

• Core escalation routes from RFC 0025: an exclusive single target or bounded conditional routes, with routed handoff provenance and complete retained reasons.
• The base and extended document ceiling profiles from RFC 0026, including reader negotiation and explicit refusal of an unsupported profile.
• The non-normative rule-overlap check and its closed JPS-RULES-OVERLAP diagnostic.
• RFC 0020's bulk amendment: contributing-rule output records, disposition summaries, reproducible seeded samples, drift comparison, and the closed workflow schema and hand-written fixture that verify those records.
• RFC 0020's later-sibling rule, limited to instances admitted for acquisition so an admission failure retains its own finding.
• Dialect data-quality conversions, reconciliation, typed research-result states, lineage, versioned source profiles, resolved settings, and byte-retaining replay contracts.
• RFC 0022's alignment with the landed composition decisions for subgraph bounds, routed handoff provenance, dialect-owned remapping, and cross-installation packaging.

Versioning and maturity

Pre-1.0.0 Core releases may be incompatible when their notes record the change and give a specVersion migration note. Conformance manifest status is now the independent maturity ladder draft, candidate, and release; 0.3.0 remains draft. The release maturity is reserved for the 1.0.0 standards claim after the governance acceptance evidence is met and recorded. Production use does not by itself establish that claim.

The Policy companion remains on its independent policy-v1.0.0-draft.N route until that format's first release and is not renamed by the Core scheme change.

RFC 0024 and the Policy companion's record land in the release if merged before the tag.

Migration note

Packs targeting this release declare exact specVersion 0.3.0. Reader and writer compatibility is not inferred from a shared 0.x prefix: historical readers reject this selector, and 0.3.0 profiles and routed escalations require corresponding reader support. Writers targeting 0.2.0-draft must obey its historical schema, which admits neither profile nor escalation routes. Multiple-version readers dispatch on the complete selector; they do not apply current rules to old selectors or rewrite old documents on read.

Carrier admission is tighter: Unicode escapes in the UTF-16 surrogate range must form well-formed surrogate pairs. For example, a lone \uD800 title escape accepted by the published 0.2.0-draft carrier and structural schema is malformed in 0.3.0. A version-only edit cannot repair those bytes. The author must provide the intended scalar or valid surrogate pair; automatic replacement would lose meaning.

Selector-only migration is sufficient only for documents that already meet the current carrier, structural and semantic requirements. Revalidate profile/ceiling support and escalation shapes; otherwise review and edit the content deliberately. No general automatic migration or unchanged conformance-verdict promise is made. Re-declaration also selects the exact new evaluator semantics and corpus, not inherited evaluator conformance. The Runtime must vendor the exact resulting artifacts beside historical releases and retain exact-selector dispatch; it must not overwrite the existing 0.2.0-draft artifacts.

Preserved historical schema identities

Historical resources come from immutable source tags, not mutable pre-repin main: v0.1.0-draft is commit 80958f50c851e9809cb8036a23622391cf437c99, and v0.2.0-draft is commit 0f30fd7b2c3fd7792249c8f3c5335b9e697a2c7a. The two 0.1.0-draft resources retain the already documented neutral-domain $id substitution and no other byte change, as recorded in the 0.2.0-draft preservation note. The three 0.2.0-draft resources are byte-identical to their original tagged forms, including research-preview maturity and the original structural rules. Their historical identities remain published; new maturity values and profile/routes rules apply only to the current resources.

The evaluation manifest schema remains at https://judgmentpack.org/schema/0.2.0-draft/conformance/evaluation/manifest.schema.json; the historical Core and document-manifest $id paths also remain served. The Core bundles carry all five preserved resources. Separately pinned Policy consumer bytes and format digests are unchanged.