Repository navigation
Releases
prism-code: v0.9.5
0.9.5 (2026-11-16)
Features Added
- prism-code: a rule app's page asks for every module at once and keeps its kernel's library load as an image (#709) (ed8c819)
- prism-code: a rule app's page reuses what this browser already fetched and proved (#706) (4dc9e88)
- prism-code: prove and build a rule app with no Docker, modelled in LexLean (#692) (#694) (81af326)
Breaking Changes
None.
Bugs Fixed
prism-code: v0.9.4
prism-code: v0.9.3
prism-code: v0.9.2
prism-code-testing: v0.1.1
prism-code: v0.9.1
prism-code: v0.9.0
0.9.0 (2026-11-14)
Features Added
- holo: holo v5 is a UORC archive named by κ (ADR-017) (#663) (7b48b4d)
- prism-code: a draft form of prism/spec/1, so a model only translates (#667) (cdced92)
- prism-code: prism/spec/2, a sealed JSON spec for apps that keep state (#665) (33a4b48)
- A draft form of
prism/spec/1, so a model only translates (#666, experimental). A draft holds what the user said: atitle, thefields, therulesand theotherwiseanswer, and leaves out any ofpurpose,outcomes,propertiesandexamples.completeSpec(src/journey/complete.mjs, pure: no clock, no randomness, no I/O) turns it into an ordinary whole spec, the same bytes from the same draft: the answers the rules give, in first-appearance order; a purpose from the answers and the fields and a name from the title; the first request each rule decides and one forotherwiseas examples, at most six; and, when the draft has fewer than three guarantees, proposals read off the rules, up to three in all, each kept only when no request breaks it and each with awhythat starts "Proposed by Prism". A spec that holds all four members is not a draft: it comes back as before and nothing is proposed again, so a struck guarantee stays struck. It is stillprism/spec/1; there is no new schema version. prism_spectakes a draft and completes it, returningproposed(the ids of proposed guarantees) andnotes; a draft written toprism/spec.jsonis completed when Prism next reads it. The review lists proposed guarantees first, marked as proposed. Theprism_specinput no longer requirespurposeandoutcomes. The MCP instructions and the skill tell a model to write only what the user said, compactly, and a guarantee only when the user stated one.- A number field compared with a bare word that names another number field (
"value": "limit") is read as that field ({"field": "limit"}) when a spec is passed toprism_spec, and named innotes: a number is never compared with text, so it has one meaning. Measured with Qwen3 30B, it was every refusal of a rules-only draft. Readingspec.jsonstrictly still refuses it, now saying how to write it. - Two clean-ups when a spec is passed to
prism_spec, each named innotes: aninvalidlisted among the answers that no rule,otherwiseor guarantee answers is dropped (it used to be refused asoutcomes.reserved), and a guarantee whose conditions no request can meet is dropped, only when every candidate request was tried. The storedspec.jsonis the spec after the drops, and its address is the seal. checkSpeccompletes and checks a spec in one call, andrepairMessagesays what to tell its author: a guarantee the rules break is named as the JSON that was written, beside the rule that decides against it and the request that shows the conflict, with the two ways out; any other refusal is given in the checker's words.prism_specreturns it asrepair.DRAFT_JSON_SCHEMAandSPEC_JSON_SCHEMA(src/journey/spec-schema.mjs):prism/spec/1as JSON Schema, the draft form and the whole spec, for a caller that can hold a model's answer to a schema. Both are closed, and number bounds are whole and not negative.prism/spec/2, the JSON spec of an app that keeps state between steps (#664,docs/proposals/664-stateful-spec.md, experimental). Boundedstatewith a start,actionswith inputs and ordered rules whosechangesets, adds to or subtracts from the state, anotherwiseper action, properties over every reachable state, and examples as sessions. It is read as strictly asprism/spec/1, with its own registered refusals (STATEFUL_REFUSALS), renders to the same bytes from the same JSON, and carries the same seal,[prism/spec/2 blake3:<hex>], soprism-code check --specholds a stateful app to its JSON. Lean proves the bounds and each property by induction over a session's steps, every theoremlinear_arithmetic. A session runs on the text profile as one request, its steps separated by;, answered with the last outcome and the state.prism_spectakes either schema; a model still writes only JSON. A stateful app builds on this machine only for now: the GitHub template is for decision apps.- An unknown
schemain a spec is refused asspec.schema, naming both schemas, rather than as an unknown member.
Breaking Changes
- holo: holo v5 is a UORC archive named by κ (ADR-017) (#663)
Bugs Fixed
v0.4.0
PrismPM 0.4.0
PrismPM 0.4.0 retains the production-system SDK released as 0.3.0 — locked
product-release construction, OCI distribution, Compose and Kubernetes 1.36.4
targets, lifecycle and recovery operations, supply-chain policy, immutable
standards/oracle imports, and the UOR template/action SDK entrypoint — and adds
the 0.4.0 capabilities listed in CHANGELOG.md: language-1.2
notation sources beside language 1.1, the prism.toml manifest, holo
inspection and verification surfaces, capability sets, and the right-sized CI.
The Holo/1 application profile is retained.
The exact adopted editions, acquired source hashes, executable oracle hashes,
and covered/uncovered requirements are recorded in standards.lock; that lock
is normative and is included in the SDK image. A passing imported schema or
finite upstream corpus is reported only at that scope. This release makes no
standards-certification, universal-correctness, untested-provider, or
unsupported SLSA-level claim.
Supported deployment targets are the pinned Compose implementation and
Kubernetes 1.36.4/Kind profile. GitHub Pages remains the portable Calculator
application publication target, not the stateful production-service target.
Provider-specific managed-cloud adapters are not included.
The release publishes six separately signed multi-platform OCI identities:
the complete SDK, the generated-browser runtime, Compose/Kubernetes/GitHub
Pages adapter packages, and the redistributable oracle-runner package. Release
assets record each manifest-list and per-platform digest; consumer locks pin
the manifest-list digests rather than the 0.4.0 discovery tags.
Holo/1 is unchanged. prism-stdlib 0.2 adds production-system model APIs while
preserving the accepted 0.1 application APIs. Product releases are immutable:
promotion, deployment, rollback, and recovery select the exact OCI digest.
The separately authorized contract-migration phase can raise the compatible
data floor; PrismPM then refuses a release below that floor.
Security reports: use the private vulnerability-reporting facility in the
GitHub Security tab for UOR-Foundation/PrismPM.
Verification begins with immutable identities published in this release:
sha256sum --check SHA256SUMS
cosign verify \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity-regexp '^https://github.com/UOR-Foundation/PrismPM/.github/workflows/release.yml@refs/tags/v0\.4\.0$' \
ghcr.io/uor-foundation/prismpm-sdk@sha256:DIGEST
docker run --rm ghcr.io/uor-foundation/prismpm-sdk@sha256:DIGEST prismpm --versionReplace DIGEST only with the manifest-list digest in the signed release
assets; tags are discovery names and are not verification or deployment
identities.
PrismPM OCI/native b48ee2ffa4d2097685054dc350b57aa204fc7080
PrismPM OCI/native verification candidate
Source: b48ee2f
These immutable OCI/native assets passed the workflow prerequisites and are published for verification.
This phase does not publish Cargo packages, versioned discovery aliases, or an accepted SDK/ecosystem release.
Each platform has complete raw SPDX in a separately signed OCI artifact, not an inline SPDX attestation.
Source V&V evidence is bound to its content identity in factory-route.json; independent SDK acceptance remains separate.
Public Cargo qualification and ecosystem acceptance are separate later phases.
PrismPM OCI/native 354038b14c26913b475c8a2cf0294051cb4fd632
PrismPM OCI/native verification candidate
Source: 354038b
These immutable OCI/native assets passed the workflow prerequisites and are published for verification.
This phase does not publish Cargo packages, versioned discovery aliases, or an accepted SDK/ecosystem release.
Each platform has complete raw SPDX in a separately signed OCI artifact, not an inline SPDX attestation.
Source V&V evidence is bound to its content identity in factory-route.json; independent SDK acceptance remains separate.
Public Cargo qualification and ecosystem acceptance are separate later phases.