You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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: a title, the fields, the rules and the otherwise answer, and leaves out any of purpose, outcomes, properties and examples. 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 for otherwise as 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 a why that 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 still prism/spec/1; there is no new schema version.
prism_spec takes a draft and completes it, returning proposed (the ids of proposed guarantees) and notes; a draft written to prism/spec.json is completed when Prism next reads it. The review lists proposed guarantees first, marked as proposed. The prism_spec input no longer requires purpose and outcomes. 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 to prism_spec, and named in notes: 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. Reading spec.json strictly still refuses it, now saying how to write it.
Two clean-ups when a spec is passed to prism_spec, each named in notes: an invalid listed among the answers that no rule, otherwise or guarantee answers is dropped (it used to be refused as outcomes.reserved), and a guarantee whose conditions no request can meet is dropped, only when every candidate request was tried. The stored spec.json is the spec after the drops, and its address is the seal.
checkSpec completes and checks a spec in one call, and repairMessage says 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_spec returns it as repair.
DRAFT_JSON_SCHEMA and SPEC_JSON_SCHEMA (src/journey/spec-schema.mjs): prism/spec/1 as 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). Bounded state with a start, actions with inputs and ordered rules whose change sets, adds to or subtracts from the state, an otherwise per action, properties over every reachable state, and examples as sessions. It is read as strictly as prism/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>], so prism-code check --spec holds a stateful app to its JSON. Lean proves the bounds and each property by induction over a session's steps, every theorem linear_arithmetic. A session runs on the text profile as one request, its steps separated by ;, answered with the last outcome and the state. prism_spec takes 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 schema in a spec is refused as spec.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
prism-code: the 0.8.0 changelog entry lists its sections in the required order (#671) (d017786)