Skip to main content

​
Releases

Prism is a single-tenant per-user install with ongoing migration. Major versions carry the release-shape semantics: a coherent set of themes shipped together, an upgrade path, and a name a reader can ask about a year from now and get a clean summary back. For the day-by-day curated arcs that compose into a release, see the Changelog. The two surfaces are companions:
  • Releases (this page) — what shipped at the major-version level. Headline themes, breaking changes, upgrade notes. One entry per release.
  • Changelog — chronological per-arc detail. One section per date when something substantive landed.

​
v0.X — Memory activation, cloud bring-up, four-level identity (2026-05-09)

The third tagged release since v0.2.0. Spans 2026-04-27 → 2026-05-09. Three thematic arcs landed together with several supporting fix arcs.

​
Headline themes

  • Memory activation layer. The substrate (TriGraph + Hybrid RAG four-leg recall + session deltas) was already shipped through v0.2.0. This release adds the activation layer that makes the substrate compulsory under stuckness: Memorules (SPEC-094 v0.5 + Phase 2 a–d, 50 unit tests) for persona-scoped behavioral memory; Dewey (Recallgate) (SPEC-099 v0.2 + Phase 3) for the advisory layer that surfaces relevant prior memorules / postmortems / decisions at the moment of action; wrap-time pre-flight (SPEC-096 v0.2 + slices 1–4) that catches ratified-but-uncommitted artifacts at prism_wrap time. Working names pending legal clearance.
  • Cloud bring-up. Phase 0 + Phase 1 of the Render Blueprint (SPEC-087) shipped end-to-end: render.yaml Blueprint, containerized Neo4j inside the prism-neo4j pserv, OAuth redirect URI threading, port-contract + dockerCommand fixes, neo4j plan upgrade to pro_plus. Plus SPEC-089 Cloud Customer Onboarding + Auth (Phase 1 provider-agnostic identity + Phase 2 WorkOSProvider with /whoami + /logout surfaces). The Blueprint applies cleanly against a fresh Render workspace.
  • Four-level identity hierarchy. SPEC-093 introduces Tenant → Org → Department → Project as the canonical identity chain, replacing the prior flat tenant/project model. Personal-install backwards compatibility preserved through flat-LAN seeding (when no Department is specified, a default Department is created under the default Org under the default Tenant — existing single-user installs continue to work without operator action). Plus SPEC-090 prism_adopt verb for registering an existing git repo into Prism without recreating PIDs.

​
Supporting arcs

  • Method fragments published. Miranda (Wallbreak Protocol) v0.2 — the canonical method fragment for the stuckness-and-persistence protocol — landed in docs/method-fragments/method.wall-break.persistence.md. Plus method.agent-operating-doctrine + method.windows-codex-incident-activation recovered from stash and published.
  • Plan #003 implementation plan. Sequences SPEC-094 Memorules + SPEC-099 Dewey (Recallgate) + SPEC-096 wrap-pre-flight into a coherent multi-phase execution arc.
  • Dashboard topology. Host name surfaced on agent + service nodes; HOSTNAME passed through to the dashboard container as PRISM_MACHINE_ID.
  • Signal-quality fix arc (RCA c3fb59b3). Canonical PID label on system_signals_emitted_total; zero-subscriber emits treated as queued with agent → session fall-back; stale session resurrection loop stopped; Redis pattern subscribers no longer count for push gating.
  • Smoke hardening. Tier-3 recall payload shapes, rollback per-key PUT + count-preservation guard + SERVICE_ID self-resolve, deploy-status live polling, https assertion on redirect_uri.
  • PDF archive. Project seed-input PDFs preserved under docs/inputs/ for ownership and timestamp record.

​
Breaking changes

  • None at the LAN tier. Personal-install operators upgrade in place.
  • At the cloud tier, OAuth flows now require https for redirect_uri (SPEC-089 + uvicorn --proxy-headers fix). Pre-cloud installs are unaffected.
  • BIOS v2.5.0 deprecates host-editor local auto-memory (SPEC-094 phase 1). All persistent memory operations route through Prism verbs (prism_remember, prism_journal, semantic_recall, etc.). Operator-locked rule — only the operator can re-enable, and only after SPEC-094 acceptance criteria pass. Existing local memory artifacts are deprecated; do not consult them as truth.

​
Upgrade

  • Personal install (LAN). prism update (one-liner) — pulls latest, rebuilds the CLI, re-runs prism install idempotently, refreshes the personal-stack container images. Equivalent fallback if you’d rather drive each step by hand: cd Prism && git pull --ff-only origin && cd cli && npm install && npm run build && prism install.
  • Cloud install. Apply the updated render.yaml Blueprint to your Render workspace; the migration sequence is 040 → 041 → 042 → 043 (alembic). SPEC-093 hierarchy + SPEC-089 cloud auth land together.

​
Detail

For the per-day chronological detail, see the changelog entries 2026-05-06, 2026-05-07, 2026-05-08.

​
v0.2.0 — Tagged baseline (2026-04-26)

The second tagged release and the start of semantic-versioning discipline for Prism. Prior to this point, the project was a single-tenant per-user install with ongoing migration; v0.2.0 anchored the line so subsequent releases could be tagged.

​
Headline themes

  • Hybrid RAG four-leg fusion. Vector + lexical + graph + temporal recall through a single semantic_recall surface (SPEC-059, ADR-018, Plan #8). Reciprocal Rank Fusion across the four legs; per-leg telemetry on every recall event.
  • Plan #10 Governance Foundation. Three artifacts ratified in a single 3.5-hour arc: ADR #47 v0.2 (governance layer precedence + override semantics), SPEC-077 v0.2 (canonical boot + governance resolution), ADR #48 v0.2 (persona / identity / specialization field model). Plus Wave 2 (SPEC-078 consensus-first parallelism + method fragments, SPEC-079 memory domain contracts + CI loop) and Wave 3 (SPEC-080 v0.2 Tri-Graph governance recall + capability index). All shipped default-off behind feature flags.
  • Operator-driven master handoff. SPEC-082 v0.3 introduced two new MCP verbs that turn master election from “implicit first-registered wins” into an explicit operator surface: prism_master_handoff(pid, to_identity) for cooperative transfer + prism_master_claim(pid, to_identity, operator_id, operator_password) for operator-authorized preempt. Plus extended MasterPreempted payload carrying previous_master_* and new_master_* fields and a reason discriminator.
  • Standalone Session Manager. Session lifecycle and signaling separated into a standalone container alongside the backend. Operators upgrade by git pull + rebuilding the backend image + the optional standalone session-manager container.

​
Supporting arcs

  • SPEC-082 hotfix arc. Controller-row Redis leak (postmortem f7ff9a8e) — silent-reconnect + cross-machine force-preempt paths now release Redis state immediately. Split-flush ordering fix (postmortem 695d29b3) — handoff_master and claim_master now demote-then-promote in separate flushes to satisfy migration 016’s partial-UNIQUE constraint.
  • prism_session_deregister surgical cleanup verb. Idempotent; releases both the Postgres controller row and the Redis hash + sessions-set entry for one session_id.
  • Per-persona daemon (SPEC-070). Always-on listener bridge with turn-boundary-preserving delivery.
  • Signal Bus QoS (SPEC-071). Delivery classes, TTL, recall verb, recipient state.

​
Detail

For the per-day chronological detail, see changelog 2026-05-04 and 2026-05-05.

​
v0.1 — Pre-tagged history (2026-04-26 and earlier)

Prior to v0.2.0, Prism shipped through a series of un-tagged but coherent arcs: PrismGR rebuild → tri-graph adoption (SPEC-020) → personal install consolidation (SPEC-053 Node CLI cutover, SPEC-054 Python MCP elimination) → hybrid recall (SPEC-059 four-leg fusion). For full history of these pre-tagged arcs, see the Prism History page (which covers the multi-name evolution: DFW → PrismGR → Prism) and the changelog entries from 2026-05-03 backwards.

​
Conventions

Release vs Changelog. A release entry summarizes a major version at the thematic level — what shipped, why it matters, what to upgrade to. A changelog entry captures a daily curated arc of what landed since the last update. Both surfaces are maintained: changelog updates per commit-arc, releases update per major version. They cross-link rather than duplicate. Working names. Several names introduced in v0.X (Memorules / Wallbreak / Recallgate / Prismorphs / Prismemoricy / Veeger / Miranda / Dewey / Janus) are working names pending legal clearance. They appear in technical / spec / engineering documentation under the archetype-primary convention (Miranda (Wallbreak Protocol) first prose mention) per the internal naming glossary. They will release together once cleared; no individual early releases. Status badges. Where a feature shipped behind a feature flag, the release entry says so explicitly (e.g., default-off). Where a feature is partially implemented, the release entry names the SPEC + phase status.
Last modified on May 9, 2026