Draft · 0.6.0

A `0.x` draft in production use by adopters: pin the exact draft and runtime release; no compatibility guarantee between drafts.

Informative View current source

v0.5.0

On this page

0.5.0, tagged v0.5.0, is the Core release that carries RFC 0031, annotations and annotated value sets (#301). Packs declare exact specVersion 0.5.0, and the tag equals the selector, as for 0.3.0.

  • Why 0.5.0 and not 0.4.0. The text was staged under the working selector 0.4.0-draft, which was never released. Tag v0.4.0 (2026-11-02) carries specVersion 0.3.0 unchanged. Under the release numbering rule VERSIONING.md now states, a tag's major and minor numbers are those of the specVersion it carries, so the number 0.4.0 is taken and no specVersion 0.4.0 is assigned. v0.4.0 is that rule's recorded exception and is unchanged.
  • The draft selector. A 0.5.0 reader refuses a pack declaring 0.4.0-draft, by the exact selector. A pack written to the draft moves up by changing its specVersion to 0.5.0, which changes its bytes and digest, and must then satisfy the released rules (Core §11).
  • Tag v0.3.0 still identifies Core 0.3.0. Its schemas stay published at their 0.3.0 identifiers, byte for byte, and its text and corpora stay at that tag.

Candidate period

None. The maintainer waived the candidate period: no release candidate precedes v0.5.0, and no adopter period was run. Implementations admitted the staged artifacts under 0.4.0-draft before the release, experimentally and outside every conformance claim.

Included work

  • Annotations and value sets (RFC 0031, #301). Short labels on the pack, its outcomes and rules in the reserved extension org.judgmentpack.annotations, optional and never required; named value sets at the pack's root, whose entries may carry descriptions and annotations; and an in condition that may name a set in place of an inline list. An evaluator gives a conforming pack the result of its evaluation form, with annotations removed and references expanded, so well-formed labels are inert and a reference equals its inline list (Core §8.5). An extensions object is one the schema defines as a member of a Core object (Core §9.1). Core §§9.2 and 10 bind what a consumer displays or filters (D2 and D1), and six ceilings join Core §4.1's table.
  • Identifiers without line terminators (#308). A local identifier, an extension name, a pack version or a decimal operand that ends in a line terminator is refused in every engine.
  • Cases that hold one defect each (#304). Two document cases staged with a second finding were corrected before the release.
  • The reserved prefix ends in its dot. Three valid cases, added after the round-1 review, pin that only names beginning org.judgmentpack. are reserved: org.judgmentpackx.a, optional and required, and the two-label name org.judgmentpack are admitted (Core §9).
  • The case schemas. The document manifest names the reader profiles its cases run under (readerProfiles), and a case may list every finding it gives (expectedDiagnostics). The evaluation case schema admits specification-defined names in a supported-extension set, and the evaluation manifest names its paired rows (pairs) and the rows whose packs are their own evaluation form (ownEvaluationForm).
  • A second evaluator. tools/core_050_eval.py, written from the text by the drafting model's vendor, runs every evaluation row and document case. It is a test tool and makes no conformance claim.
  • Beside Core. An informative concept page, Roles in a record (#275); JSON Schemas for three record formats that had none (#286); and two amendments of Draft RFC 0030 (#284, #291). None changes Core.

RFC 0031 is Accepted on its round-1 review, by a model from the drafting vendor, with the different-vendor review the interim regime asks for waived by the maintainer. That is a same-vendor review, not a cross-vendor claim. The record's Acceptance section states each item of its evidence bar. Item 3, two independently authored implementations passing every staged vector, is met in part: both implementations are by the drafting vendor, both refuse the 18 document cases that declare the extended profile, which neither supports, and the reference runtime passed the vectors staged at c867b35 (208 document cases and 82 rows) but has not run the seven cases #308 added, the two fixtures #304 rewrote, or anything under 0.5.0. The maintainer directed acceptance on that basis; the reference runtime's take-up of 0.5.0 is the follow-up.

Compatibility

  • Reader compatibility: a 0.3.0 reader refuses a pack declaring 0.5.0, by the exact selector, and the 0.3.0 schema refuses each new shape.
  • Writer compatibility: a writer targeting 0.3.0 emits neither annotations nor value sets.
  • Semantic compatibility: for a pack that uses neither feature, the evaluation form is the pack, so 0.5.0 changes no result for it, apart from one shape Core §9.1's reading of an extensions object refuses.
  • Migration compatibility: for almost every 0.3.0 pack, changing only the selector is enough, and evaluation is unchanged. Core §11 names the exceptions.

Migration note

Packs targeting this release declare exact specVersion 0.5.0. Core §11 states the migration from 0.3.0: a local identifier, an extension name, a pack version or a decimal operand that ends in a line terminator is refused in every engine, and a pack whose required name appears only under a member named extensions inside data must also add the name as a key of an extensions object the schema defines. Labels kept in a vendor extension may be moved to the reserved name by hand; there is no automatic coercion. Each such edit changes the bytes, so the pack should receive a new version.

A conformance claim is made against exact specVersion 0.5.0 and the corpora published with it, and is not inherited from 0.3.0. Multiple-version readers dispatch on the complete selector. The reference runtime must vendor the 0.5.0 artifacts beside the historical ones, keep exact-selector dispatch, and not overwrite the 0.3.0 artifacts.

The selected retained-column leaf

Stay on the v0.3.0 bundle for the retained-column/1 leaf. That release is the leaf's normative support distribution, and support version 0.3.0 does not change. Core 0.5.0 changed four files the v0.3.0 inventory pins (spec/judgment-pack-core.md, spec/dialect.md and the two dialect readers' vector code); their v0.3.0 bytes are preserved in the repository's historical fixtures, and the inventory itself is unchanged.

Preserved historical schema identities

The four 0.3.0 schemas that Core 0.5.0 replaced in place stay published at their 0.3.0 identifiers, byte-identical to the files tag v0.3.0 published:

Preserved file $id SHA-256
schema/judgment-pack-core-0.3.0.schema.json https://judgmentpack.org/schema/0.3.0/judgment-pack-core.schema.json 4ef5040ba5aeecc00bf4a23aca82812900a136d2119285bf1dac78b71ac64639
schema/conformance-manifest-0.3.0.schema.json https://judgmentpack.org/schema/0.3.0/conformance/manifest.schema.json 3d14efea2186a0d630c5d980c683bca8b4d4576dbf7213ed6cc37e8199016fdf
schema/conformance-evaluation-manifest-0.3.0.schema.json https://judgmentpack.org/schema/0.3.0/conformance/evaluation/manifest.schema.json 930d4c4e22ddc54f29c35090d6c979ad4e798c939509a7d6fac325c0dfd783da
schema/workflow-1-0.3.0.schema.json https://judgmentpack.org/schema/0.3.0/workflow-1.schema.json b306eb4d96b5ff4edfa87e7b7e86fbac12b9d3d347f8f513a396217464075d6f

The workflow contributor model

https://judgmentpack.org/schema/0.4.0/workflow-contributors-2.schema.json is not published by this release, as it was not by v0.4.0. That $id is draft staging from RFC 0028, a Draft, and is left as it stands. RFC 0028's own target line still names Spec 0.5.0; this release does not carry it. The file schema/workflow-contributors-2.schema.json is in these bundles as it was in the v0.3.0 and v0.4.0 bundles, and the site serves it at that path. Neither establishes a release of it: its format-status record stays baseline null and lastReleased null.

What is in the bundles

The .tar.gz and .zip bundles, with their checksums and build-provenance attestations, hold:

  • the Core and companion prose under spec/, without the Draft spec/workflow.md;
  • schema/ and conformance/, without the Policy companion's directories or the staged directories (conformance/dialect/, conformance/witness/, conformance/evaluation/staged/);
  • examples/;
  • README.md, LICENSE, NOTICE, CHANGELOG.md, VERSIONING.md, TESTING.md and SECURITY.md; and
  • this file.

They do not hold catalog/, which joined v0.4.0's bundles only, rfcs/, tools/, requirements-dev.txt, the other files in releases/, the leaf inventories, or a generated release-identity.json: this release has no distribution mapping, because its tag is its specVersion.

Versioning and maturity

Conformance manifest status stays draft. In catalog/format-status.json this release is the baseline and the last release of the four families whose $id is under 0.5.0: judgment-pack-core, conformance/manifest, conformance/evaluation/manifest and workflow. The other families keep their records.

What this release pins

  • Format: exact specVersion 0.5.0, the Core schema's specVersion constant and the selector both corpus manifests name.
  • Frozen corpora: conformance/manifest.json (369 conformance cases and 5 advisory cases) and conformance/evaluation/manifest.json (103 rows, 29 pairs), both suiteVersion 0.5.0 at maturity draft. A conformance claim names these corpora and requires every applicable row to pass; conformance/evaluation/errata.md lists no errata for 0.5.0.
  • Core schema: https://judgmentpack.org/schema/0.5.0/judgment-pack-core.schema.json, SHA-256 fb182fd0ab7fc303618ce9a63834616527a68b63b165e7ed3e76f48f29978da0.
  • Document-manifest schema: https://judgmentpack.org/schema/0.5.0/conformance/manifest.schema.json, SHA-256 d835195ecf4c0f214d78d106256f9b61fa006d4888a1b7c115c65b837d0496ed.
  • Evaluation-manifest schema: https://judgmentpack.org/schema/0.5.0/conformance/evaluation/manifest.schema.json, SHA-256 7bc20cd13d074c56d151f90bd72ed8bed8d3bbd1481fcfe9218987652aafa1e8.
  • Workflow document schema: https://judgmentpack.org/schema/0.5.0/workflow-1.schema.json, SHA-256 74b13dc5b1cbf011ddefbb43490d4f615b20238033fd910feecfd10207e1907b.

Checks run for this release

The release reuses main's repository-conformance evidence for this exact commit through the release evidence gate (scripts/dev/release_evidence.py, configured by .github/ci-evidence.json) instead of running the repository suite again. The milestone, tag, artifact-pin and bundle checks run again at the tag. The reused run's id and attempt are in the gate's decision record, which the release run keeps as its release-evidence-<attempt> artifact (web/DEPLOYMENT.md, "Release evidence").

RFC 0031 and its staged artifacts were reviewed in round 1 (rfcs/reviews/0031-round-1.md). That is same-vendor review, not a cross-vendor claim. The #308 content and the #304 fixture corrections postdate the round-1 review and were covered by the review of the graduation pull request, also by the same vendor, whose findings added the three reserved-prefix cases.

Results against this release name its tag and commit. Conformance never proves truth, authorization, safety or operational fitness.