Repository navigation
Add shared offline Policy document tooling after companion adoption #293
Description
Track the Runtime part of Judgment-Pack/judgment-pack-spec#211 / draft PR #212. Runtime owns offline init/schema/validation, exact retained-byte references and canonical identity for the eventual accepted Policy/adoption contract, exposed through shared CLI/MCP capabilities. Reuse artifact version parsing/calculation; do not infer publication authority or compatibility from a bump.
Acceptance: exact supported selectors and capability discovery; closed-format and semantic/reference checks; original/narrative separation; UTF-8 section anchors; governing coverage and exact consuming pack identity; strict rejection of unsupported required references; staged valid/invalid/boundary vectors. Preserve Core's own JSON domain and exact pack bytes—optional Policy canonicalization must not silently reject otherwise valid pack extension numbers.
Depends on the portable contract's review/adoption. The current RFC Python prototype is review material, not a released Runtime capability or independent implementation evidence. Runtime must not become a team/IAM, source-fetching, live publication or current-admission service.
Activity
kikashy commentedon Oct 18, 2026
Starting an explicitly experimental first slice under this issue after Spec PR #212 was merged as a Draft RFC/non-normative prototype. The maintainer has temporarily waived different-vendor review for the current Policy work; the recorded Codex reviews remain same-vendor. This does not adopt a released companion or change the general repository review rule.
Implementation uses GPT-6.1 Sol workers: xhigh for shared validation/canonical/reference contracts, high for CLI/MCP integration and documentation. Work is isolated from the maintainer's uncommitted Runtime checkout.
Planned surface:
jpack experimental policyand clearly named experimental MCP tools for contract discovery, starter documents, schema, canonicalization/digest, document validation and exact supplied-material checks. Both use one shared offline Go implementation pinned to prototype0.0.2. Existing strict JSON, artifact-version, offline schema and canonical boundaries are reused. Materials are explicit retained bytes; no provider/network retrieval, project writes or approval inference. Original/narrative/consumer identities stay separate, and raw Core numbers retain Core's own domain.Acceptance: vendored source/fixture integrity; the three synthetic domains; malformed selectors/carriers/UTF-8/references; original, role, aggregate and transport bounds; raw/canonical distinctions; CLI/MCP parity and no-write/no-network behavior. Focused local checks precede repository CI. This issue's eventual adopted-companion/production claims remain open; no live lifecycle, governing registration, execution admission or independent interoperability evidence is implied.
kikashy commentedon Oct 18, 2026
The first experimental Runtime slice is merged in PR #294 as
dd7974d62beec54160ed48b3c893d9509db60bd4. It pins non-normative Policy prototype0.0.2at Spec8a56a95d555c17640d2db4984363b779536b3c2aand exposes shared offline CLI/MCP contract, init, schema, canonicalize, digest, validate and check operations.It checks exact supplied documents and retained evidence, with raw and canonical identity kept separate, UTF-8 anchors, scoped coverage, typed consumer references and bounded inputs. It reuses the existing strict carrier, artifact version grammar, schema compiler and canonical encoding. These checks do not establish approval, publication, current governing authority, full Core semantics or run admission.
Same-vendor clean-room findings were fixed: deterministic capped diagnostics, numeric preflight before schema conversion, and safe shared MCP argument refusals. The current maintainer-authorized different-vendor exception is recorded on the PR; no different-vendor or independent implementation agreement is claimed.
This issue remains open for the eventual adopted companion contract, capability/version updates and corresponding released integration. Spec #212 merged a Draft RFC and prototype, not normative adoption. No Runtime release or running Desk activation is part of this change.
All final PR checks passed on Linux (stable and Go 1.24), macOS and Windows, plus DCO and the MCP registry template. The exact reviewed source passed 21 native CLI/MCP smoke checks; the final packaging change preserved all 29 vendored files under Windows-style checkout. CI: https://github.com/Judgment-Pack/judgment-pack-runtime/actions/runs/39152737422
Prepare Runtime v0.35.0 release (#295)
kikashy commentedon Oct 18, 2026
Experimental candidate support is now merged in #296 as
0554c43d2bea08e06b9a1e7be39834494ee29d5e(reviewed source55a23b884f0ce67fe6a9141b04e081a518fd5d61; identical tree). It pins Spec0852c5f, merged via Spec #217. Default prototype reports/discovery remain compatible; explicit discovery and format dispatch share the existing offline engine.Validation: all 124 portable vectors; 124 additional cross-reader URI probes; relevant Policy/MCP/CLI/validation tests and vet; final Linux (stable/1.24), macOS and Windows CI; unchanged Desk exact-material/refusal and shared-material archive/restore tests against the final binary. Three review findings—URI grammar, refusal ordering and Windows checkout byte conversion—are resolved. Final review: #296 (comment) .
The candidate remains proposed-draft at RFC Review. This issue stays open for accepted-contract support after formal adoption; the default Core URI correction is tracked separately in #297. No live authority, acquisition, IAM, signing trust or execution admission was added.
Release hold preserved: Runtime v0.35.0 remains the existing unpublished draft at
5157249; its tag/assets are not repurposed for #296. No release gate, OCI/MCP publication, Desk pin merge, install or restart occurred. A future distribution decision must identify the correct later Runtime source explicitly.kikashy commentedon Oct 19, 2026
The adoption prerequisite is now met at draft maturity. Spec PR #218 merged as
0799b37b74e35c4a86bfbf70f7bee80bdb7bbe94, and the independently versioned immutable prerelease policy-v1.0.0-draft.1 is published. Official prose isspec/policy.md, document format is exactly1.0.0, and Core remains unchanged. The release manifest pins the official schemas, prose and complete 124-row offline-reader corpus. Limited public review and draft maturity are explicitly recorded; there is no stable or independently authored interoperability claim.Runtime v0.36.0's existing CLI/MCP init, contract discovery, schema, canonicalization/digest, validation and retained-reference checking remain experimental and pinned to their earlier Spec bytes. They are not retroactively upgraded by this publication.
Next bounded Runtime work under this issue:
draftcapability/result maturity.Desk can then deliberately adopt that release and recheck its shared authoring/coverage/recovery integration. Runner and Gateway need compatibility checks; a new release is needed only if their actual contracts or behavior change. Team/IAM, live source fetching, publication authority and current dispatch admission remain outside Runtime.
kikashy commentedon Oct 19, 2026
Implementation is proceeding under the maintainer's request to finish official Policy adoption and the release path before local Desk testing.
The new Runtime release will deliberately repin explicit format
1.0.0to immutablepolicy-v1.0.0-draft.1/ Spec0799b37b74e35c4a86bfbf70f7bee80bdb7bbe94. Grammar promotion does not rewrite retained Policy/adoption bytes. Schema identities, capability/result maturity (draft) and provenance change; strict clients comparing complete result objects must deliberately adopt the new Runtime contract. Prototype0.0.2defaults/reports and legacy candidate vendor evidence stay intact. Existing experimental CLI/MCP names and candidate result field names remain compatible transport names; neither implies stable maturity or authority.The bounded implementation reuses the existing reader, imports exact official schemas/capabilities/reader corpus/prose with per-file provenance, and must pass all 124 official rows. Encoding/local validation remain narrower than full retained-material checking. Full Core semantics, signatures, IAM, source fetching, current approval and dispatch admission remain excluded. No document/approval/Job migration or Core pin change.
Desk is being updated separately to use exact official metadata for fresh checks while retaining exact legacy report validation for historical evidence. Existing frozen Jobs and records remain on their original pins. Required CI and a bounded independent same-vendor review use the existing temporary different-vendor waiver, stated honestly. Held Runtime v0.35.0 remains unpublished; local Desk remains running and real user data/providers are untouched.
kikashy commentedon Oct 19, 2026
Delivered in immutable Runtime v0.37.0, source
bde356c084c1e7786e0a6c327addcd16ec856ebc(reviewed treee68f2c0d97a2e6df51be9b8dc8e961fd62bbaa0b). The signed tag and all six actual platform archives/checksums/restricted build attestations were verified. Release 39320833434 passed all 12 jobs, including native archive checks, OCI publication, anonymous amd64/arm64 image smoke, image promotion/attestation and MCP registry publication.Explicit format 1.0.0 now identifies the official Policy draft. All 124 exact source corpus results passed; the shipped Linux binary separately passed one exact official example check. Prototype defaults and historical candidate bytes remain preserved. Offline checks do not confer authority or stable/independently authored interoperability. Held Runtime v0.35.0 remains unpublished.
Desk adoption is delivered separately in Desk #535 / v0.13.1, including strict fresh checks and exact historical report verification. Independent Codex review is recorded honestly as same-vendor under the user's temporary exception.