Judgment Pack Specification v0.3.0-rc.2

v0.3.0-rc.2

This second Core release candidate adds exactly selected retained-column/1 support accepted
at draft maturity through RFC0029. Acceptance and
a draft GitHub release are separate from immutable publication: publication requires the exact
tag, maintainer-published GitHub release and verified artifacts. Core packs declare specVersion 0.3.0, while the
selected leaf names exact distribution version 0.3.0-rc.2, source revision and schema/corpus pins.
This is no final Core, stable interoperability or general preparation-verifier conformance claim.

The accepted design's scope is selected retained columns.
Its closed inventory binds new schema, complete shared corpus,
prose and offline owners; release-identity.json supplies the exact commit without self-reference.
The release build must include those bytes in both archives, checksums and provenance. The existing 47 historical
Dialect recordings remain staged and are not published by this leaf corpus.

Readers refuse unknown exact pins/roles before artifact admission. Writers emit new leaves only
for supported selections. Ordinary documents, absence of optional members, old carrier/preparation
versions, all five conversions/eight original types and retained provenance keep their contracts.
Changed raw rules/frames/inventories require fresh commitments and the existing review/CAS gates.
There is no automatic rewrite of old publications, recipes, receipts or subscriptions.

Published v0.3.0-rc.1, its source/tag/assets/mapping/notes and preserved public schema resources
remain immutable. RC2 retains final v0.3.0 milestone #2. The maintainer records reasonable public
feedback and the treatment of RC2 changes before final Core publication; these notes establish no
completed final Core adopter period or final release gate. Final exact-version conformance still requires the
final published corpus. Same-vendor review under the authorized exception is identified accurately.
The corrected maximum-envelope ledger and its source/history premises are recorded on the
adoption disposition;
the original proof table is superseded. That record closes C1 and dispositions the pre-adoption
RFC comments at draft maturity without claiming outside-adopter feedback. The final Core adopter
period and feedback gates remain required. Real producer/history support, production Desk cutover and exact-head
product/release verification are not inferred from these draft artifacts or synthetic fixtures.
Acceptance does not complete Agent #171.