v0.5.2
On this page
v0.5.2 carries Core specVersion 0.5.0 unchanged, as v0.5.1 does, under the release
numbering rule of VERSIONING.md. What it adds is beside Core: the annotation
vocabulary 1.0.0, status proposed, a companion document that gives one annotation key,
severity on an outcome, a closed and ordered set of values.
- Packs keep declaring exact
specVersion0.5.0. A pack declaring0.5.2is refused, because the Core schema'sspecVersionconstant is still0.5.0. - The tag name is not a selector.
0.5.2is this distribution's identity, as each bundle's generatedrelease-identity.jsonrecords it. No reader, pack or claim selects it, and no pack declares the vocabulary's version either. - Core
0.5.0's normative files are byte for byte those tagv0.5.0released, as the recordreleases/v0.5.0.normative.jsonnames them. Both corpora keepsuiteVersion0.5.0. The builder refuses a patch tag, or a bundle, whose files differ from that record. - A pack Core accepted, it still accepts; a pack it refused, it still refuses; and every evaluation gives the result it gave.
- Tags
v0.5.0andv0.5.1are not changed or superseded. Consumers pinned tov0.5.0orv0.5.1need do nothing.
Included work
- The annotation vocabulary
1.0.0, proposed (#320). RFC 0032, accepted at draft maturity on 2026-11-13, adds a companion document with its own version,spec/annotation-vocabulary.md. It defines: - the key
severityin an outcome's annotations, and at no other position (§2.1); - four levels,
low<medium<high<critical, matched by code point, one string and never a list; absence states no severity and has no default (§2.2 to §2.5); - a vocabulary checker (§6), which applies only to
specVersion0.5.0, admits the pack under Core first and says why whenever it does not apply the vocabulary, then refuses any other value, and any list, withJPS-VOCABULARY-SEVERITY-VALUE, with a recommended advisory,JPS-VOCABULARY-SEVERITY-IDENTIFIER, for an outcome identifier whose last segment is a different level (§3.1); and - how a view shows, orders and filters levels (§4), informative except for the statements that stop a view misstating the author, and no suggested action (§5).
The key is inert: Core §8.5's evaluation form already removes outcome annotations, so no Core
rule changes (§2.6). One key is defined, not a registry (§8). The companion is normative for the
vocabulary-checker class, and for a consumer that applies it in the statements §4 marks MUST or
MUST NOT. Core 0.5.0 §1.1 does not list it, because a release that carries Core 0.5.0 changes
no Core text.
- Its rows and its reader. 32 hand-written rows and one pair (three packs, five facts
documents), with the machine-readable form vocabulary.json, are staged under
conformance/annotation-vocabulary/1.0.0/. They are not a conformance corpus, they are in no
bundle, and no claim may cite them. The repository's checker, tools/annotation_vocabulary.py,
is the one reader; no second, independently written reader exists.
- The review it was accepted on. One review round by a model from the drafting vendor is copied
verbatim to rfcs/reviews/0032-round-1.md: one HIGH, six MEDIUM and seven LOW findings, each
fixed before the record merged. The maintainer waived the different-vendor review of
RFC 0009.
This release closes #320.
Compatibility
Nothing in Core moves, so each dimension VERSIONING.md names has the same answer between v0.5.1
and v0.5.2:
- Reader compatibility: unchanged. A
0.5.0reader reads what it read, and need not read the vocabulary. - Writer compatibility: unchanged. Writers emit
specVersion0.5.0. - Semantic compatibility: unchanged. Conforming consumers assign the same portable meaning, and the vocabulary's key is inert in evaluation.
- Migration compatibility: no document transformation applies, because no Core document changes.
| Release | Core specVersion 0.5.0 |
Annotation vocabulary 1.0.0 |
|---|---|---|
Specification v0.5.0 and v0.5.1 |
released; carried unchanged | not defined |
Specification v0.5.2 |
carried unchanged, byte for byte | proposed (spec/annotation-vocabulary.md); the companion in the bundles, its rows in none |
Reference runtime v0.44.0 and later |
read; no change needed | no released version checks it; a later, unpublished runtime release may, with no version promised |
| Reference Runner | as its own release notes state; no change needed | no released version checks it |
| Reference gateway | no change needed | no change needed |
A pack whose outcomes already use a key named severity with other values stays Core-conforming
and evaluates as before; only a vocabulary checker refuses it.
What a pack author does
Nothing is required. A pack that states no severity is unaffected. An author who wants a pack to state how serious an outcome is:
- adds
"severity": "high", or another level, to that outcome's annotations, the object atextensions→org.judgmentpack.annotations; the value is one oflow,medium,highandcritical, written exactly so (§2.2, §2.4), and one string, never a list (§2.5); - leaves the key out of an outcome that states no seriousness: there is no
none, and absence is notlow(§2.3); - keeps the level out of the outcome identifier, writing
referwith"severity": "high", notrefer-high(§3); - keeps
specVersion0.5.0and declares no vocabulary version; a project that requires the check names the checker and version1.0.0in its own tooling or process (§7); and - can run the repository's checker at the tag,
python tools/annotation_vocabulary.py check PACK. Its result is the vocabulary checker's, not a Core result, and no conformance claim may cite it.
Adding or changing a level changes the pack's bytes, and so every digest over them, and changes no evaluation result (§2.6).
Migration note
None. There is no specVersion to migrate to. A conformance claim stays against exact specVersion
0.5.0 and its corpora, and is neither widened nor renewed by this release. No claim names the
annotation vocabulary.
The selected retained-column leaf
Stay on the v0.3.0 bundle for the retained-column/1 leaf, as for v0.5.0 and v0.5.1. That
release is the leaf's normative support distribution, and support version 0.3.0 does not change.
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/, now withspec/annotation-vocabulary.md, and without the Draftspec/workflow.md; schema/andconformance/, without the Policy companion's directories or the staged directories (conformance/annotation-vocabulary/,conformance/dialect/,conformance/witness/,conformance/evaluation/staged/);examples/;catalog/, which a patch release's bundles carry;README.md,LICENSE,NOTICE,CHANGELOG.md,VERSIONING.md,TESTING.mdandSECURITY.md; and- this file, the record
releases/v0.5.0.normative.jsonand the generatedrelease-identity.json.
Beside the v0.5.1 bundle, this bundle adds spec/annotation-vocabulary.md and holds this file in
place of releases/v0.5.1.md. Of the files both hold, only these differ: README.md,
CHANGELOG.md, catalog/format-status.json, whose four 0.5.0 families now name this release, its
example in catalog/README.md, and the generated release-identity.json.
They do not hold:
rfcs/, so RFC 0032 is read at the tag or on the site, and its review at the tag;- the vocabulary's rows or
vocabulary.json; tools/, so the vocabulary checker and the builder are read at the tag;requirements-dev.txt, the other files inreleases/, or the leaf inventories; or- the Policy companion's schemas and corpus, which keep their own
policy-vroute.
Versioning and maturity
Conformance manifest status stays draft. A patch release is not a candidate, so 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. The
vocabulary adds no family: vocabulary.json has no $id and is not a schema file.
The builder holds this release, in the worktree and in each bundle, to the record
releases/v0.5.0.normative.json. It gives the SHA-256 of each of the 422 normative files of
specVersion 0.5.0: the Core text and schema, both corpus manifests, the cases and packs they
name, and every schema whose $id is under 0.5.0. The record was derived from the files of tag
v0.5.0 (commit 171d4c21d4b13e03ee20e1adb6fc5cc6b182cfae), and the builder pins the record's own
SHA-256. The companion is not in the record.
RFC 0032 is accepted at draft maturity. The annotation vocabulary 1.0.0 is proposed: its rows are
staged, one reader reads it, and no vocabulary-checker conformance claim is available.
What this release pins
- Format: exact
specVersion0.5.0, the Core schema'sspecVersionconstant and the selector both corpus manifests name. - Frozen corpora:
conformance/manifest.json(369 conformance cases and 5 advisory cases) andconformance/evaluation/manifest.json(103 rows, 29 pairs), bothsuiteVersion0.5.0at maturitydraft, byte for byte asv0.5.0released them. - Core schema:
https://judgmentpack.org/schema/0.5.0/judgment-pack-core.schema.json, SHA-256fb182fd0ab7fc303618ce9a63834616527a68b63b165e7ed3e76f48f29978da0, as inv0.5.0. - Document-manifest schema:
https://judgmentpack.org/schema/0.5.0/conformance/manifest.schema.json, SHA-256d835195ecf4c0f214d78d106256f9b61fa006d4888a1b7c115c65b837d0496ed. - Evaluation-manifest schema:
https://judgmentpack.org/schema/0.5.0/conformance/evaluation/manifest.schema.json, SHA-2567bc20cd13d074c56d151f90bd72ed8bed8d3bbd1481fcfe9218987652aafa1e8. - Workflow document schema:
https://judgmentpack.org/schema/0.5.0/workflow-1.schema.json, SHA-25674b13dc5b1cbf011ddefbb43490d4f615b20238033fd910feecfd10207e1907b. - Normative record:
releases/v0.5.0.normative.json, SHA-25686e175e8786eb6e08a215178ba7099edb074193c83c5ee2dc6a12012555b4aaa. - Distribution identity:
releaseVersion0.5.2, tagv0.5.2,specVersion0.5.0,distributionspecification-unchanged, with the source commit in each bundle'srelease-identity.json.
What this release does not establish
- A different-vendor review. RFC 0032 was accepted on a review by a model from the drafting vendor, and the maintainer waived the review RFC 0009 asks for. That is same-vendor review, not a cross-vendor claim.
- A second reader.
tools/annotation_vocabulary.pyis the one implementation of the vocabulary checker. The fragment invocabulary.jsonis a second reading of the refusal alone, not an independent implementation, and RFC 0000's two independent implementations, a bar for a stable feature, are not shown. - A conformance claim. The rows are in no corpus and no bundle, and no claim may cite them.
- A released consumer. No released runtime or Runner checks the vocabulary or orders a view by it. A later runtime release may, with no version promised.
- The
extendedrow. The one row whose pack declares theextendedprofile records what a checker that supportsextendedgives; the one checker supportsbaseonly, so it has not run. - Outside comment. RFC 0032 was public for less than a day before it was accepted.
- That a level is right. A level is its author's statement (§2.2, §4), and a checker reads only its spelling.
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, normative-record 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 0032, its companion and its rows were reviewed in one round (rfcs/reviews/0032-round-1.md):
one HIGH, six MEDIUM and seven LOW findings, each fixed. That is same-vendor review, not a
cross-vendor claim. The rows run through the document corpus's harness, the checker, the
repository's second Core evaluator and a general JSON Schema validator
(tests/test_annotation_vocabulary.py). The companion's place in the bundles and on the site, and
the rows' absence from both, each have a test that fails when it is changed.
Results against this release name its tag and commit. Conformance never proves truth, authorization, safety or operational fitness.