v0.6.0
On this page
0.6.0, tagged v0.6.0, is the Core release that carries the dialect formats 4.0.0 and 4.1.0
and a workflow stage that names them (#326, #328). Packs declare exact specVersion 0.6.0, and
the tag equals the selector, as for 0.5.0.
- Core's rules are
0.5.0's. No carrier, structural, semantic or evaluation rule differs. A0.5.0pack whose selector alone is changed to0.6.0keeps every verdict and every disposition (Core §11). The selector moves because this release changes what the companion texts admit, and a tagvX.Y.0carriesspecVersionX.Y.0(VERSIONING.md). - The selector. A
0.6.0reader refuses a pack declaring0.5.0, by the exact selector, and a0.5.0reader refuses one declaring0.6.0. Changing the selector changes the pack's bytes and digest. - Tag
v0.5.0still identifies Core0.5.0, andv0.5.1andv0.5.2carry it unchanged. Its schemas stay published at their0.5.0identifiers, byte for byte, and its text and corpora stay at those tags.
Candidate period
None. The maintainer waived the candidate period: no release candidate precedes v0.6.0, and no
adopter period was run.
Included work
- Dialect format
4.0.0(spec/dialect.md§2.2). A rule on the case, list and decimal parameter types, rule version2.0.0with ordered comparison, membership, a forward freshness window and literal claim values, and three built-in derived values in exact integer arithmetic. RFC 0018's amendments of 2026-11-12 and 2026-11-13 are adopted for0.6.0; the format was first carried, as proposed, byv0.5.1. - Dialect format
4.1.0, a pagedoperationsource (spec/dialect.md§2.3, #328). RFC 0033 is accepted. Anoperationsource may declarepaging: its pages are one gateway session's calls 0 to n−1, each with its own signed receipt, each request after the first formed from the first and the page before; the loop ends at a page that names no next reference or at a declared bound, and the preparation records which. The pages' records are joined in call order, duplicates kept, and the source's read applies once.pageItemsstays refused. AprevSignatureat odds with its receipt's own call index isacquisition-invalid(#326). - Recordings of both formats (#326). Version 2 of the dialect-recording schemas,
schema/dialect-recording/2/, informative, describes a preparation of format4.0.0or4.1.0and an export carrying one. Version 1 is unchanged and reads the earlier forms. - A workflow stage of either format (#326). RFC 0020's amendment of 2026-11-15 is accepted for
0.6.0: such a stage takes no Runner encoding, and its release digest is SHA-256 of thecanonbytes of the whole retained release, which is open beyondid,packDigest,runtimeDigestandinputMapping. The workflow document schema of0.6.0adds both formats to a named dialect reference. RFC 0020 stays a Draft, andspec/workflow.mdstays normative for nothing. - Readers. The Python dialect reader reads both formats; the TypeScript reader refuses both
version-unread. The workflow reader reads a stage of either, digests its release by the stage's rule, and checks a paged source's profile fit. - Tests that do not read the live tree (#319). The patch-release tests hold the builder to a
hand-authored fixture and a test-local normative record, so they do not change when
mainmoves to a newspecVersion.
The reviews are those recorded on pull requests 329, 330, 331 and 332, by a model of the drafting vendor. That is same-vendor review, not a cross-vendor claim; the maintainer waived the review by another vendor for this work.
Compatibility
- Reader compatibility: a
0.5.0reader refuses a pack declaring0.6.0, by the exact selector. A dialect reader written to an earlier text refuses a document of format4.1.0input-malformed, and one written to this text that does not read a format refuses itversion-unread; neither reads part of one. - Writer compatibility: a writer targeting
0.5.0keeps emitting0.5.0. A dialect with no paged source has no reason to take format4.1.0. - Semantic compatibility: for every pack,
0.6.0changes no result. No answer, digest, preparation or vector of dialect format2,3,2.0.0,3.0.0or4.0.0changes, and no release digest of a stage of format2.0.0or3.0.0, or of integer version2or3, changes. - Migration compatibility: changing only the selector is enough (Core §11).
Migration note
Packs targeting this release declare exact specVersion 0.6.0; nothing else in a pack changes.
The edit changes the bytes, so the pack should receive a new version. A conformance claim is made
against exact specVersion 0.6.0 and the corpora published with it, and is not inherited from
0.5.0. Multiple-version readers dispatch on the complete selector and keep the 0.5.0 artifacts
beside the new ones.
The selected retained-column leaf
Stay on the v0.3.0 bundle for the retained-column/1 leaf, as for every 0.5.x release. That
release is the leaf's normative support distribution, and support version 0.3.0 does not change.
Preserved historical schema identities
The four 0.5.0 schemas that Core 0.6.0 replaced in place stay published at their 0.5.0
identifiers, byte-identical to the files tag v0.5.0 published:
| Preserved file | $id |
SHA-256 |
|---|---|---|
schema/judgment-pack-core-0.5.0.schema.json |
https://judgmentpack.org/schema/0.5.0/judgment-pack-core.schema.json |
fb182fd0ab7fc303618ce9a63834616527a68b63b165e7ed3e76f48f29978da0 |
schema/conformance-manifest-0.5.0.schema.json |
https://judgmentpack.org/schema/0.5.0/conformance/manifest.schema.json |
d835195ecf4c0f214d78d106256f9b61fa006d4888a1b7c115c65b837d0496ed |
schema/conformance-evaluation-manifest-0.5.0.schema.json |
https://judgmentpack.org/schema/0.5.0/conformance/evaluation/manifest.schema.json |
7bc20cd13d074c56d151f90bd72ed8bed8d3bbd1481fcfe9218987652aafa1e8 |
schema/workflow-1-0.5.0.schema.json |
https://judgmentpack.org/schema/0.5.0/workflow-1.schema.json |
74b13dc5b1cbf011ddefbb43490d4f615b20238033fd910feecfd10207e1907b |
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 Draftspec/workflow.md; schema/, now withschema/dialect-recording/2/, andconformance/, without the Policy companion's directories or the staged directories (conformance/annotation-vocabulary/,conformance/dialect/,conformance/witness/,conformance/evaluation/staged/);examples/;README.md,LICENSE,NOTICE,CHANGELOG.md,VERSIONING.md,TESTING.mdandSECURITY.md; and- this file.
They do not hold catalog/, which a patch release's bundles carry, 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. The vectors of formats 4.0.0 and 4.1.0, of the recording schemas and of the
workflow stages are under conformance/dialect/, so no bundle carries them.
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.6.0:
judgment-pack-core, conformance/manifest, conformance/evaluation/manifest and workflow. The
other families keep their records; dialect-recording, whose $ids name no specVersion, keeps a
null baseline.
What this release pins
- Format: exact
specVersion0.6.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.6.0at maturitydraft. They are0.5.0's cases and rows with the selector moved. A conformance claim names these corpora and requires every applicable row to pass. - Core schema:
https://judgmentpack.org/schema/0.6.0/judgment-pack-core.schema.json, SHA-256d9e116c240e1136ada3e307cbf6035ec8fc202539d31b4dfc57e228248f97ae1. - Document-manifest schema:
https://judgmentpack.org/schema/0.6.0/conformance/manifest.schema.json, SHA-2561778978455f6be54a7816b49073a0f6e6962e596e4edb7788bc32702df4ac449. - Evaluation-manifest schema:
https://judgmentpack.org/schema/0.6.0/conformance/evaluation/manifest.schema.json, SHA-256048c3d405c438f0f762e2970c86e8090111744f59e0bfc2df5f37726fefd4610. - Workflow document schema:
https://judgmentpack.org/schema/0.6.0/workflow-1.schema.json, SHA-256c534da6e1e098fa5809799b2ccf73e2a1421445777864939501816afc25d1235. - Dialect-recording schemas, version 2, informative:
https://judgmentpack.org/schema/dialect-recording/2/export.schema.json, SHA-256971ac8c4f79bc0bb78b9a72e7e565456455276b8ff2e86039b02b4680b0be1fb, andhttps://judgmentpack.org/schema/dialect-recording/2/preparation.schema.json, SHA-256ecf216d468699fade10068130b897ff60915151d311ad1b0f029f2f7d5074345.
What this release does not establish
- A different-vendor review. The work was accepted on reviews by a model from the drafting vendor, and the maintainer waived the review RFC 0009 asks for.
- A conformance claim for either dialect format. Their vectors are hand-written, in no corpus
and no bundle, and no claim names either format (
spec/dialect.md§14). - A second reader of either format. One of the repository's two dialect readers reads them; the
TypeScript reader refuses both
version-unread. - The reference Runner's agreement. The reference Runner prepares paged sources since its pull
request 299 (
v0.34.0). This repository runs none of its tests, and no Runner recording of either format is among the vectors. - Recordings under
0.5.0or0.6.0. The recording readers read0.2.0-draftand0.3.0recordings alone; reading later ones is a follow-up. - The annotation vocabulary under
0.6.0. The vocabulary1.0.0and its checker apply tospecVersion0.5.0; admitting0.6.0is a follow-up.
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").
Results against this release name its tag and commit. Conformance never proves truth, authorization, safety or operational fitness.