sage
(S)AGE - (Sovereign) Agent Governed Experience
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/l33tdawg/sage with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/l33tdawg/sage'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/l33tdawg--sage)HTML
<a href="/listings/l33tdawg--sage"><img src="/api/listings/l33tdawg--sage/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
**Desktop:** [Download the latest release](https://github.com/l33tdawg/sage/releases/latest), open SAGE and complete setup in CEREBRUM. Choose your memory engine, connect an AI client and review agent access. Follow the [connection guide](https://l33tdawg.github.io/sage/connect.html) for your tool or the full [Getting Started](docs/GETTING_STARTED.md) walkthrough.
If SAGE is already running, check it before starting another server:
curl http://127.0.0.1:8080/health
A healthy node returns `{"status":"healthy"}`. After connecting an MCP client, call `sage_inception` and follow its returned memory mode.
<details> <summary>Build from source</summary>
**From source (Go 1.26.8+):**
git clone https://github.com/l33tdawg/sage.git && cd sage go build -o sage-gui ./cmd/sage-gui/ ./sage-gui setup # Pick your AI, get MCP config ./sage-gui serve # SAGE + Dashboard on :8080
</details>
Desktop packages: [macOS DMG](https://github.com/l33tdawg/sage/releases/latest) (signed & notarized) | [Windows EXE](https://github.com/l33tdawg/sage/releases/latest) | [Linux tar.gz](https://github.com/l33tdawg/sage/releases/latest)
<details> <summary>Docker and containerized MCP setup</summary>
Docker
docker pull ghcr.io/l33tdawg/sage:latest docker run -d --name sage \ -p 8080:8080 \ -v ~/.sage:/root/.sage \ ghcr.io/l33tdawg/sage:latest
Pin a specific version with `ghcr.io/l33tdawg/sage:11.23.15`.
The SAGE server stays in that container. To give a local MCP client a stdio bridge, start a second process **inside the same running container**:
docker exec -i \ -e SAGE_PROVIDER=claude-code \ -e SAGE_PROJECT=my-project \ -e SAGE_IDENTITY_PATH=/root/.sage/agents/claude-code-my-project/agent.key \ sage /usr/local/bin/sage-gui mcp
For the shipped Compose stack, use the service name rather than a generated container name:
docker compose -f docker-compose.sage-gui.yml exec -T \ -e SAGE_PROVIDER=claude-code \ -e SAGE_PROJECT=my-project \ -e SAGE_IDENTITY_PATH=/root/.sage/agents/claude-code-my-project/agent.key \ sage /usr/local/bin/sage-gui mcp
If an MCP client launches this through a wrapper, point its stdio configuration at the wrapper's absolute path. Pass `SAGE_PROVIDER`, `SAGE_PROJECT`, and `SAGE_IDENTITY_PATH` through `docker exec -e`/`docker compose exec -e`; setting them only on the host-side Docker command does not place them in the container. Keep the whole SAGE data root mounted at `/root/.sage`, including agent keys and the ledger. Do not start a separate `docker run ... mcp` container: its `localhost:8080` is isolated from the running SAGE server.
HTTP MCP is also available at `/v1/mcp/sse` and `/v1/mcp/streamable`, but both require a bearer token or OAuth. Bare `http://localhost:8080` is the REST base, not an unauthenticated MCP endpoint.
</details>
<details> <summary>Upgrading an existing node</summary>
Upgrading from an older version?
**Upgrading an existing node — including the v10.x → v11 jump — is [docs/UPGRADING.md](docs/UPGRADING.md).** In the desktop app, accept the update: SAGE verifies canonical upgrade compatibility, captures a full recovery snapshot, installs, and restarts automatically. Headless and quorum operators have separate technical procedures in the guide. Your chain advances in place; a personal node climbs the consensus fork ladder by itself. Read the guide before a multi-admin chain crosses app-v23 — that activation re-derives administrator authority.
If you installed SAGE before v5.0 and your AI isn't doing turn-by-turn memory updates, re-run the installer in your project directory:
cd /path/to/your/project sage-gui mcp install
This installs Claude Code hooks that prompt the memory lifecycle (boot, turn, reflect) — even if your `.mcp.json` is already configured. Restart your Claude Code session after running this.
</details>
---
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 2,701 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # (S)AGE — Sovereign Agent Governed Experience
- 
- **Memory your agents can be held to.**
- SAGE is a governed memory and messaging layer for AI agents. Every memory is
- signed by an agent, admitted through a reviewable process, scoped by permissions
- you set, and kept with an audit trail you can inspect.
- Connect your tools to the same local node so authorized agents can record
- experience and recall relevant context in later sessions. Inspect what they keep
- in CEREBRUM, SAGE's local dashboard.
- Works with Claude Code, Codex, Cursor and other MCP-capable clients. Developers
- can integrate through the Python SDK or signed REST API. Recall depends on what
- is recorded, your configuration and the agent's use of its tools.
- [Download SAGE](https://github.com/l33tdawg/sage/releases/latest) ·
- [Get started](https://l33tdawg.github.io/sage/#get-started) ·
- [Connect your AI](https://l33tdawg.github.io/sage/connect.html) ·
- [Developer quickstart](https://l33tdawg.github.io/sage/#developers)
- [Why SAGE](#why-sage) · [Quick Start](#quick-start) · [For Developers](#for-developers) · [Architecture](#architecture) ·
- [Capabilities](#current-capabilities) · [Dashboard](#cerebrum-dashboard) ·
- [Release history](#release-history) · [Documentation](#documentation)
- <a href="https://glama.ai/mcp/servers/l33tdawg/s-age">
- <img width="380" height="200" src="https://glama.ai/mcp/servers/l33tdawg/s-age/badge" alt="(S)AGE MCP server" />
- </a>
- ---
- ## Why SAGE
- Use SAGE when your agents return to ongoing work: a design decision worth
- keeping, an approach that failed, or a lesson the next session should use.
- RAG retrieves source material; SAGE uses retrieval too, with a governed record
- of agent experience around it.
- - **Trace the origin.** Agent-signed writes attribute memories to their recorded author.
- - **Review admission.** Memories pass through a validation lifecycle before they enter normal recall.
- - **Control access.** Enrollment, domain permissions and classification determine which agents can use a memory.
- - **Keep memory useful.** Inspect confidence and status, apply decay, or deprecate a memory while retaining its audit history.
- A personal install runs one validator and casts its own signed admission vote.
- A multi-validator network requires a BFT quorum. These checks govern what is
- committed; they do not prove every remembered claim is true or change your
- model's weights. See the [memory lifecycle](docs/reference/concepts/memory-lifecycle.md)
- and [consensus reference](docs/reference/concepts/consensus-confidence-decay.md).
- Memory is local by default. Optional federation, connectors and remote model
- providers can send data to configured destinations. Enable the vault for
- memory-content encryption at rest; see the [privacy details](https://l33tdawg.github.io/sage/privacy.html)
- and [Security FAQ](SECURITY_FAQ.md).
- ## Quick Start
- **Desktop:** [Download the latest release](https://github.com/l33tdawg/sage/releases/latest),
- open SAGE and complete setup in CEREBRUM. Choose your memory engine, connect an
- AI client and review agent access. Follow the
- [connection guide](https://l33tdawg.github.io/sage/connect.html) for your tool or
- the full [Getting Started](docs/GETTING_STARTED.md) walkthrough.
- If SAGE is already running, check it before starting another server:
- ```bash
- curl http://127.0.0.1:8080/health
- ```
- A healthy node returns `{"status":"healthy"}`. After connecting an MCP client,
- call `sage_inception` and follow its returned memory mode.
- <details>
- <summary>Build from source</summary>
- **From source (Go 1.26.11+):**
- ```bash
- git clone https://github.com/l33tdawg/sage.git && cd sage
- go build -o sage-gui ./cmd/sage-gui/
- ./sage-gui setup # Pick your AI, get MCP config
- ./sage-gui serve # SAGE + Dashboard on :8080
- ```
- </details>
- Desktop packages: [macOS DMG](https://github.com/l33tdawg/sage/releases/latest) (signed & notarized) | [Windows EXE](https://github.com/l33tdawg/sage/releases/latest) | [Linux tar.gz](https://github.com/l33tdawg/sage/releases/latest)
- <details>
- <summary>Docker and containerized MCP setup</summary>
- ### Docker
- ```bash
- docker pull ghcr.io/l33tdawg/sage:latest
- docker run -d --name sage \
- -p 8080:8080 \
- -v ~/.sage:/root/.sage \
- ghcr.io/l33tdawg/sage:latest
- ```
- Pin a specific version with `ghcr.io/l33tdawg/sage:11.25.8`.
- The SAGE server stays in that container. To give a local MCP client a stdio
- bridge, start a second process **inside the same running container**:
- ```bash
- docker exec -i \
- -e SAGE_PROVIDER=claude-code \
- -e SAGE_PROJECT=my-project \
- -e SAGE_IDENTITY_PATH=/root/.sage/agents/claude-code-my-project/agent.key \
- sage /usr/local/bin/sage-gui mcp
- ```
- For the shipped Compose stack, use the service name rather than a generated
- container name:
- ```bash
- docker compose -f docker-compose.sage-gui.yml exec -T \
- -e SAGE_PROVIDER=claude-code \
- -e SAGE_PROJECT=my-project \
- -e SAGE_IDENTITY_PATH=/root/.sage/agents/claude-code-my-project/agent.key \
- sage /usr/local/bin/sage-gui mcp
- ```
- If an MCP client launches this through a wrapper, point its stdio configuration
- at the wrapper's absolute path. Pass `SAGE_PROVIDER`, `SAGE_PROJECT`, and
- `SAGE_IDENTITY_PATH` through `docker exec -e`/`docker compose exec -e`; setting
- them only on the host-side Docker command does not place them in the container.
- Keep the whole SAGE data root mounted at `/root/.sage`, including agent keys and
- the ledger. Do not start a separate `docker run ... mcp` container: its
- `localhost:8080` is isolated from the running SAGE server.
- HTTP MCP is also available at `/v1/mcp/sse` and `/v1/mcp/streamable`, but both
- require a bearer token or OAuth. Bare `http://localhost:8080` is the REST base,
- not an unauthenticated MCP endpoint.
- </details>
- <details>
- <summary>Upgrading an existing node</summary>
- ### Upgrading from an older version?
- **Upgrading an existing node — including the v10.x → v11 jump — is
- [docs/UPGRADING.md](docs/UPGRADING.md).** In the desktop app, accept the update:
- SAGE verifies canonical upgrade compatibility, captures a full recovery
- snapshot, installs, and restarts automatically. Headless and quorum operators
- have separate technical procedures in the guide.
- Your chain advances in place; a personal node climbs the consensus fork ladder by
- itself. Read the guide before a multi-admin chain crosses app-v23 — that
- activation re-derives administrator authority.
- If you installed SAGE before v5.0 and your AI isn't doing turn-by-turn memory updates, re-run the installer in your project directory:
- ```bash
- cd /path/to/your/project
- sage-gui mcp install
- ```
- This installs Claude Code hooks that prompt the memory lifecycle (boot, turn, reflect) — even if your `.mcp.json` is already configured. Restart your Claude Code session after running this.
- </details>
- ---
- ## For Developers
- Choose an integration for your workflow:
- | Integration | Use it for | Start here |
- | --- | --- | --- |
- | MCP | Giving an existing AI client memory and coordination tools | [Connection guide](https://l33tdawg.github.io/sage/connect.html) · [MCP reference](docs/reference/mcp-tools.md) |
- | Python SDK | Building a memory-aware agent or application with sync/async clients | [Developer quickstart](https://l33tdawg.github.io/sage/#developers) · [SDK reference](docs/reference/python-sdk.md) |
- | Signed REST API | Integrating from another language over HTTP | [REST reference](docs/reference/rest-api.md) |
- The [authoritative reference index](docs/reference/INDEX.md) covers exact API
- behavior, authentication, access controls and lifecycle rules. Start there
- when implementing an integration.
- ### Python: read existing memories
- Requires Python 3.10+, a running node and an enrolled agent. Set
- `SAGE_IDENTITY_PATH` to that agent's existing key file and `SAGE_DOMAIN` to a
- domain it can read.
- ```bash
- python -m pip install sage-agent-sdk
- ```
- ```python
- import os
- from sage_sdk import AgentIdentity, SageClient
- identity = AgentIdentity.from_file(os.environ["SAGE_IDENTITY_PATH"])
- domain = os.environ["SAGE_DOMAIN"]
- with SageClient(
- base_url="http://127.0.0.1:8080",
- identity=identity,
- trust_env=False,
- ) as client:
- page = client.list_memories(
- domain=domain, status="committed", limit=3,
- )
- for memory in page.memories:
- print(memory.memory_id, memory.content)
- ```
- Save as `quickstart.py` and run `python quickstart.py`. An empty list means no
- committed memories are visible to this agent in that domain. Review enrollment
- and domain permissions in CEREBRUM if access is denied.
- To record experience, use `propose()` in a domain the agent can write to and set
- classification explicitly. A submitted memory starts as `proposed`; normal
- recall includes it after admission commits it. For semantic retrieval, use
- `hybrid()` with query text and a matching embedding. See the
- [SDK examples](docs/reference/python-sdk.md) and
- [memory admission guide](docs/reference/concepts/voter-operations.md).
- ---
- ## Architecture
- ```mermaid
- flowchart TB
- A["AI agents · MCP / SDK / REST"] --> P["SAGE node · authenticated admission + live policy"]
- H["CEREBRUM · local human control"] --> P
- P --> M["Memory + local policy transactions<br/>CometBFT / ABCI"]
- P --> W["Node-local coordination<br/>inbox / claims / replies"]
- M --> B["BadgerDB<br/>authoritative chain state"]
- B --> Q["Commit-time SQL projection<br/>content + vectors for authorized recall"]
- P -. "explicit peer trust and sharing" .-> F["Separate SAGE chain<br/>bounded Read / receiver-controlled Copy"]
- classDef entry fill:#eef2ff,stroke:#6366f1,color:#1e293b
- classDef memory fill:#ecfdf5,stroke:#059669,color:#064e3b
- classDef work fill:#fff7ed,stroke:#d97706,color:#7c2d12
- class A,H,P entry
- class M,B,Q memory
- class W,F work
- ```
- **Agents are not validators.** Personal mode runs one real CometBFT validator
- with a per-node memory auto-voter; it has no Byzantine redundancy. Registering
- more agents does not add consensus voters. A multi-validator deployment runs
- one shared chain; federation connects separate chains under explicit policy.
- **Storage has two roles.** BadgerDB is authoritative for consensus state.
- SQLite (personal) or PostgreSQL + pgvector (cluster) projects memory content
- and vectors at Commit. Node-local message coordination is separate from the
- memory consensus path. Block inclusion is not the same as memory acceptance.
- For the detailed trust boundaries, lifecycles, and deployment topology, see
- [Architecture & Deployment](docs/ARCHITECTURE.md).
- ## Current Capabilities
- | Capability | What it provides |
- |------------|------------------|
- | Governed memory | Persistent, attributed memories with consensus validation, semantic recall, confidence, and lifecycle controls |
- | Durable tasks | Exact-agent assigned backlog; open tasks do not decay; idempotent creation and workflow status |
- | Unified inbox | Local/federated requests, assignment notices, and a separate passive reply page |
- | Runtime handoff | Explicit session-and-revision-fenced takeover of claimed work within the same signed agent identity |
- | Access controls | Active enrollment, roles/profiles, ownership, Access Groups, compatible grants, and classification checks |
- | Controlled federation | Explicit agent exports and bounded Read/Copy policy, without granting local membership or Write |
- | Recovery and updates | In-place chain upgrades, recovery snapshots, and retained message claims across ordinary restarts |
- ### How agents collaborate
- ```mermaid
- flowchart TB
- T["Task assigned to exact agent"] --> N["One-way assignment notice"]
- N --> I["Unified inbox"]
- R["Request addressed to exact agent"] --> I
- I -->|"task notice"| V["Verify current assignment in backlog<br/>then update the task"]
- I -->|"inbound request"| C["Claimed by one MCP runtime"]
- C -->|"normal completion"| O["Idempotent reply"]
- C -. "intentional same-agent takeover" .-> H["Handoff: expected session + revision"]
- H --> O
- O --> S["Original sender reads reply_items<br/>or pages retained replies"]
- classDef input fill:#eef2ff,stroke:#6366f1,color:#1e293b
- classDef task fill:#ecfdf5,stroke:#059669,color:#064e3b
- classDef message fill:#fff7ed,stroke:#d97706,color:#7c2d12
- class I input
- class T,N,V task
- class R,C,H,O,S message
- ```
- Assignment, claim, and reply are different states. A task notice is not a
- request for a message result, and a reply is not a new assignment. Runtime
- handoff does not reassign a task to another agent. Wake notifications are
- payload-free hints, not delivery or claim evidence. Every agent request and
- result remains untrusted data, not authority to expand the user's instructions.
- See the [MCP task/inbox reference](docs/reference/mcp-tools.md) and
- [message/reply lifecycle](docs/reference/concepts/message-reply-lifecycle.md)
- for exact fields, recovery, and authorization rules.
- ---
- ## CEREBRUM Dashboard
- 
- `http://127.0.0.1:8080/ui/` — a dashboard-native operator console centered on the 3D MRI memory brain, with chain health, agents, federation, semantic memory, recall tuning, vault recovery, tasks, imports, and updates around it. Every major workflow is available from the browser; the CLI stays there for automation and recovery.
- | Control Board | Federation | Recall Engine |
- |:---:|:---:|:---:|
- |  |  |  |
- | Chain health, quorum, agents, federation, and embeddings | One trust-only JOIN that prepares Direct and Secure relay automatically, followed by independent Read/Copy choices on each SAGE | Smart-memory setup, managed reranker install, and recall-depth tuning |
- The dashboard also includes governed agent enrollment, Access Groups, domain
- permissions, separate CEREBRUM Root credential handover, import/export,
- software updates, and encryption controls. Ordinary agent identity replacement
- uses re-enrollment; historical memory authorship is preserved.
- ---
- <details>
- <summary>Recent release notes (v11.25.8 and earlier)</summary>
- ## What's New in v11.25.8
- **RFC #443 Phase A now ships node-self-minted link cards and the fleet QR JOIN
- gate.** Org policy v2 binds `peer_allow_list` entries to enrollee agent keys,
- while signed rosters and cards provide the local transport facts needed for a
- manual JOIN. Each enrolled node mints its own card from runtime identity and
- transport state, and the durable card floor rejects rollback, equivocation and a
- changed policy generation.
- A fleet-managed manual QR JOIN now checks the peer against every enrolled org's
- current policy on both host and guest at request, approval and pre-tx
- boundaries. When policy denies the peer, a current Root may sign a bounded,
- expiring local exception; both storing and listing exceptions require that Root
- through localhost, and every use is audited. Nodes without an enrollment keep
- the existing JOIN behavior.
- This release does not activate Phase B roster-introduced links, the owner
- envelope or the durable introduction state machine. No consensus version change,
- chain reset, or data migration. `latest` and automatic upgrade voting remain
- app29; app30 remains explicit. Container:
- `ghcr.io/l33tdawg/sage:11.25.8`. SDK 11.25.8.
- ## What's New in v11.25.7
- **Go 1.26.11 closes a reachable HTTP vulnerability.** GO-2026-6859 affects the
- `net/http` body reader and is reachable through SAGE's HTTP surface. Source
- builds now require Go 1.26.11, and every shipped Go source-build container uses
- that toolchain.
- The Go dependency group also moves `compress` to 1.20.4, `x/sync` to 0.25.0,
- `x/sys` to 0.50.0, `modernc.org/sqlite` to 1.62.0, and its pinned
- `modernc.org/libc` to 1.80.1. Browser fixtures move to Playwright 1.65, and the
- pinned CodeQL and Docker login actions are refreshed.
- No consensus version change, app-version change, chain reset, or data migration.
- `latest` and automatic upgrade voting remain app29; app30 remains explicit.
- Container: `ghcr.io/l33tdawg/sage:11.25.7`. SDK 11.25.7.
- ## What's New in v11.25.6
- **Direct-grant inspection now follows canonical chain state.** After app-v23,
- the ordinary grant-list endpoint takes `domain`, `grantee_id`, `granter_id`,
- `access_level`, and `expires_at` from Badger rather than the SQL serving mirror.
- A canonical grant is visible even when that projection is empty, and a canonical
- revoke disappears immediately instead of surviving as stale mirror data.
- `GET /v1/access/grants-snapshot/{agent_id}` adds a bounded exact-target snapshot
- for reconciliation. One committed Badger read supplies the caller/target
- authorization records, current Root generation, height, AppHash, and active
- direct grants. The endpoint allows self-inspection or a current local Admin,
- fails closed on incomplete or oversized reads, and is deliberately not effective
- access, a global atomic directory, or a new protocol capability.
- No consensus version change, app-version change, chain reset, or data migration.
- `latest` and automatic upgrade voting remain app29; app30 remains explicit.
- Container: `ghcr.io/l33tdawg/sage:11.25.6`. SDK 11.25.6.
- ## What's New in v11.25.5
- **MCP inbox limits now explain themselves.** `sage_inbox` keeps its bounded
- `1-20` limit for messages and task notices and for its passive reply page, but
- both caps are now explicit in the model-facing tool descriptions even when
- schema validation keywords are flattened. An out-of-range `limit` reports the
- submitted value and names the exact `message_next_cursor` and
- `task_notice_next_cursor` fields to use for continuation, so callers can page
- instead of repeatedly guessing a larger limit.
- No consensus version change, app-version change, chain reset, or data migration.
- `latest` and automatic upgrade voting remain app29; app30 remains explicit.
- Container: `ghcr.io/l33tdawg/sage:11.25.5`. SDK 11.25.5.
- ## What's New in v11.25.4
- **Snapshot retention now survives chain redeploys and stays bounded.** Snapshot
- manifests record the chain identity, and `snapshot list` and automatic retention
- order captures by time rather than by height. A redeployed chain that restarts at
- height 1 therefore keeps its newest recovery points instead of losing them to
- obsolete high-height snapshots. Retention keeps the configured number of current
- chain captures plus a bounded set of recent version anchors. Recovery executables
- are limited to the current binary and one prior copy, with stale temporary copies
- reaped safely. New snapshots use schema v2; existing v1 snapshots remain readable.
- **Release-page refreshes now fail closed on stale editorial copy.** The Pages
- snapshot job refuses to write a newer version stamp when the landing page's
- What's New block, FAQ, or version-pinned documentation links still describe an
- older release. Dynamic download counts remain automatic; release copy must move
- with them.
- No consensus version change, app-version change, chain reset, or data migration.
- `latest` and automatic upgrade voting remain app29; app30 remains explicit.
- Container: `ghcr.io/l33tdawg/sage:11.25.4`. SDK 11.25.4.
- ## What's New in v11.25.3
- **Memory submit now reports fields it did not apply.** Unknown top-level body
- keys are still accepted and ignored for compatibility, but the response names
- them in a bounded, sorted `ignored_fields` array and the node logs a warning
- without their values. This makes a correction-shaped request visible when a
- client sends fields such as `replaces_memory_id` to a route that only stores the
- replacement memory. Corrections still use submit, wait for commit, then challenge
- the old memory.
- **The Go dependency baseline closes two high-severity pgx vulnerabilities.**
- `pgx` moves to 5.12.0 for the simple-protocol batch SQL-injection and
- authentication-requirement fixes, with `puddle` 2.2.3. The SQLite driver moves
- to 1.61.1 for prepared-statement and read-only VFS correctness. The test-only
- PostgreSQL mock moves to its pgx-5.12-compatible v6 line.
- No consensus version change or chain migration. `latest` and automatic upgrade
- voting remain app29; app30 remains explicit.
- ## What's New in v11.25.2
- **Fresh-node setup imports now use the enrolled Companion identity.** On a new
- post-v23 chain, the setup wizard's pending memories previously tried to embed and
- submit as the genesis Root, which is deliberately not an ordinary agent. The
- import now signs as the enrolled Companion, routes an unqualified entry to that
- Companion's home domain, and reports embed, submit, and zero-import failures at
- visible log levels instead of producing only `Imported 0/N`.
- **The optional local memory judge is pinned to v17b.** The default-off managed
- judge now uses a separate immutable model artifact, verifies both the downloaded
- GGUF and Ollama's registered blob, and keeps explicit v16 selections unchanged.
- The v17b training pass targets the short user decisions and task-shaped memories
- that v16 often rejected or held, while retaining the chat-only and session-remark
- traps. New writing guidance is linked from the write-gate reference.
- No consensus version change or chain migration. `latest` and automatic upgrade
- voting remain app29; app30 remains explicit.
- ## What's New in v11.25.1
- **AMID can approve a distinct local agent.** Operators can opt into `--local-agent-key-dir` (`SAGE_LOCAL_AGENT_KEY_DIR`) to supply identity-bound target consent keys to the existing access-policy route and Python SDK methods. Root authorization, same-machine checks, and consensus validation remain required. Unregistered targets are refused before signing or broadcast, and malformed Ed25519 private-key encodings fail closed.
- **Hybrid recall sizes reranking work from the requested results.** The authorization scan retains its full candidate coverage while the cross-encoder scores the smaller requested pool. `SAGE_RERANK_MAX_CANDIDATES` adds an optional cap. Rate-limited fallback warnings expose operational failures without logging upstream error text or submitted content.
- **Explicit federation settings survive config saves.** Disabled P2P, an empty relay list, and disabled force-private mode no longer disappear during serialization and revert to defaults on reload.
- **Force-quitting the macOS tray no longer leaves its daemon orphaned after startup.** The tray identifies itself to its child; once graceful shutdown is ready, the daemon monitors that parent and stops if it disappears. Standalone and externally supervised daemons remain independent unless explicitly configured with the parent relationship.
- No consensus version change or chain migration. `latest` and automatic upgrade voting remain app29; app30 remains explicit. Existing reply catch-up and v11.24.4 fixes are already included through release history.
- Container: `ghcr.io/l33tdawg/sage:11.25.4`. SDK 11.25.4.
- ## What's New in v11.25.0
- **Fresh chains start at the supported app version.** A new personal `sage-gui serve`
- starts directly at app29. For a shared chain, create one signed, full-roster
- artifact with `init-genesis`, then run `init-fresh-node` on each Unix node against
- its exact genesis digest before starting `serve`. Existing chains keep their
- keys, genesis and governed upgrade history. See the
- [fresh-genesis guide](docs/reference/fresh-genesis.md).
- **App30 taint and authenticated lineage ship as explicit rules.** The merged
- implementation includes immutable multi-parent `derived_from` references,
- governed apply/clear decisions, bounded canonical traversal, provenance and
- recovery/state-sync support. `latest` and automatic upgrade voting remain at
- app29; an explicit signed app30 genesis or quorum-approved plan selects app30.
- **The native-shell control contract accepts v11.25 daemons.** Native standalone
- packages retain their preview identity and separate promotion requirements.
- Evidence-operator integration and complete count, coverage and error parity
- across clients/backends remain open in [#460](https://github.com/l33tdawg/sage/issues/460).
- Container: `ghcr.io/l33tdawg/sage:11.25.0`. SDK 11.25.0.
- ## What's New in v11.24.5
- **Task identity is now domain-aware.** App-v23 tasks use their permanent idempotency identity—caller, exact signed domain, canonical `[TASK]` content, or an explicit occurrence key—instead of the global memory-content tombstone. The same task body can exist as a distinct task in another governed domain without being deprecated after consensus.
- **Deprecated tasks can no longer mutate.** REST and the SQLite and PostgreSQL stores reject claim, completion, and status changes on deprecated task rows, so a full-ID update cannot report success against a task that has disappeared from the backlog.
- **No app-version or data migration.** App-v29 remains active. Container: `ghcr.io/l33tdawg/sage:11.24.5`. SDK 11.24.5.
- ## What's New in v11.24.4
- **macOS restarts now recover without Activity Monitor cleanup.** The tray keeps `sage-gui serve` supervised, restarts unexpected exits with bounded backoff, detects a live child that stops answering health checks, and retains the unlocked passphrase for the replacement process. Daemon logs are appended so a failed restart keeps its evidence.
- **Shutdown no longer lets transport teardown strand an update.** MCP HTTP and federation P2P close stages are bounded. A timeout is logged without rolling back an otherwise valid update or preventing the replacement process from starting.
- **CEREBRUM makes the restart wait visible.** The updater now shows a live five-minute countdown and phase-specific status while SAGE finishes in-flight work, closes its listener, starts the replacement, and reconnects. The countdown keeps moving even while a request or health probe is waiting on the network.
- **No consensus change or chain migration.** App-v29 remains active. Container: `ghcr.io/l33tdawg/sage:11.24.4`. SDK 11.24.4.
- ## What's New in v11.24.3
- **AMID exposes the signer-fence recovery surface without requiring CEREBRUM.** Operator-only `GET /v1/dashboard/signer-fence/status`, `POST /v1/dashboard/signer-fence/lift`, and `POST /v1/dashboard/signer-fence/abandon` routes now serve the cluster runtime. The exact configured governance operator must sign each request; caller-supplied proofs and evidence are rejected, request bodies are bounded, and the node rereads committed nonce, transaction, mempool, and peer state before every recovery decision.
- **AMID health now follows the external Comet engine.** After the chain identity binds, AMID continually probes the configured CometBFT RPC `/health`, clears its Comet health bit on failure, and restores it after recovery. The compose validators use `restart: unless-stopped`, preserving deliberate operator stops while restarting unexpected exits.
- **Public SAGE-Noesis outcome receipts establish an evidence-only interop boundary.** Receipt v1 is public-only, signed, off-consensus, and carries no REST or MCP route. It records reproducible control/treatment evidence without granting valuation, stake, governance, access, or memory authority to Noesis.
- **No consensus change or chain migration.** App-v29 remains active. Container: `ghcr.io/l33tdawg/sage:11.24.3`. SDK 11.24.3.
- ## What's New in v11.24.2
- **PostgreSQL stats now exclude deprecated memories from totals and per-domain counts, matching SQLite.** Status counts and last activity retain their audit history.
- **CEREBRUM timelines now include in-range memories at fractional-second date boundaries.** Whole-second and fractional bounds keep exact inclusive timestamp checks and canonical visibility checks.
- **No consensus change or chain migration.** App-v29 remains active. Container: `ghcr.io/l33tdawg/sage:11.24.2`. SDK 11.24.2.
- ## What's New in v11.24.1
- **App-v29 now activates automatically after its evidence gates pass.** The auto-vote readiness ceiling moves from app-v28 to app-v29, so personal nodes converge on the architecture-independent PoE arithmetic already compiled in v11.24.0. The activation block keeps app-v28 behavior; deterministic EWMA, recency, corroboration, logarithm, exponential and final-weight calculations begin at H+1. Historical blocks continue to replay under their original app versions.
- **The app-v29 evidence spans the real failure surfaces.** A four-validator ladder crosses app-v2 through app-v29 with byte-identical AppHash at H-1, H and H+1, then continues through the first post-activation PoE epoch. A separate quorum runs two validators and CometBFT processes on arm64 and two on amd64 against one chain. The real-process crash, partition, restart and state-sync gate targets exact app-v29 state.
- **The patch closes the release security gaps.** Go 1.26.10 fixes GO-2026-6809 in `crypto/x509`; certifi 2026.10.19 removes the compromised emSign intermediate CA bundle from all benchmark environments; and the dependency group updates chi, klauspost/compress, go-winio, Playwright and pinned GitHub Actions.
- **No chain migration.** Existing memories, identities, governance state and chain history are preserved. Container: `ghcr.io/l33tdawg/sage:11.24.1`. SDK 11.24.1.
- ## What's New in v11.24.0
- **PoE weights now have an architecture-independent path.** App-v29 compiles a new consensus form of the proof-of-experience arithmetic: EWMA state updates, recency, corroboration and final weights use explicitly rounded operations that produce the same float64 bits on arm64 and amd64. The gate remains dormant above the app-v28 auto-vote ceiling, so existing chains keep their current app version and historical blocks keep replaying under their original arithmetic until the mixed-architecture, replay, snapshot and state-sync evidence is complete. CI and release workflows now run exact golden vectors on native amd64 and arm64.
- **Org fleet enrollment Phase 1 lands.** Organizations can issue 24-hour, single-use tokens bound to one exact node key and immutable policy scope. Redemption atomically stores the consume marker, replayable result and first signed policy in node-local SQLite; concurrent attempts cannot overwrite the winner, and a lost response can be replayed even after token expiry or revocation. Signed policy delivery adds monotonic revisions, rollback protection, persisted rotation history and overlap, a durable owner-visible equivocation alarm, and per-operation offline/expiry gates for enrollment and new peering. `sage-gui org-token create|list|revoke` exposes the operator flow.
- **No chain migration.** App-v28 remains active and app-v29 remains compiled but dormant. Existing memories, identities, governance state and chain history are preserved. Container: `ghcr.io/l33tdawg/sage:11.24.0`. SDK 11.24.0.
- ## What's New in v11.23.27
- **Find the exact MCP session before a handover.** `sage_sessions` is a new read-only, self-only inventory of this agent's live MCP claimant sessions on the local node. It returns each exact `session_id`, transport kind, provider/project, whether it is the current session, liveness from the same OS advisory lock used by claimant identity acquisition, and the exact count of unfinished claims held by that session. Stale identity records are counted separately and are not presented as live sessions. The tool never claims, hands off, replies, or grants authority; session IDs remain coordination metadata, not authorization principals.
- **Access Group controls say what they do.** CEREBRUM's Access Group editor now labels its close and delete actions accurately instead of putting Delete in the conventional close slot.
- **No chain migration.** App-v28 remains active. The MCP catalog grows to 38 tools; clients with a cached catalog should re-list or reconnect. Container: `ghcr.io/l33tdawg/sage:11.23.27`. SDK 11.23.27.
- ## What's New in v11.23.26
- **App-v28 activation now succeeds on legacy public corpora.** The public-memory stage is built before the activation block's consensus transaction, so a record it could not encode aborted the activation on every replay and left the pending plan with no in-band downgrade. Records born before app-v25 whose canonical envelope lacks a domain, author, or author principal, carries a non-32-byte content hash, or carries a co-commit tombstone are now quarantined out of the committed public set instead of refusing the build. Records born under app-v25 or later still fail closed, and a recorded-but-empty or malformed field still refuses on every record. A record returns to the public set in the block that re-anchors its envelope.
- **Preflight now checks the corpus before the fork.** `sage-gui upgrade preflight` runs the same read-only census as `sage-gui upgrade public-memory-audit` when a chain still has to cross app-v28, and refuses "clear to climb" when a record would block activation. The audit names every record, the exact failed checks, and whether the stage would quarantine or refuse it. `--limit` bounds the printed list; the counters still cover the whole corpus.
- **Quarantined records are visible, not silent.** The audit reports them by memory id, and they stay outside the app-v28 public-memory tree until re-anchored. No chain migration is required; app-v28 remains active.
- Container: `ghcr.io/l33tdawg/sage:11.23.26`. SDK 11.23.26.
- ## What's New in v11.23.25
- **Unscoped recall works again on a mature node.** An app-v23 node refuses a ranked recall whose candidate set exceeds its authorization scan budget rather than ranking an arbitrary prefix. On a node with a large corpus that made a domainless `sage_recall` fail permanently — the tool's default shape. Recall now falls back once to your governed home domain and reports the effective scope in `domain`, `recall_scope` and `recall_scope_note`, so an empty home-domain result is never read as proof the memory does not exist elsewhere. An explicitly scoped recall is never redirected.
- **Federated recall is bounded, and says why it is empty.** `/v1/federation/recall-plan` now carries a server-side deadline with a per-peer budget, so one unreachable peer can no longer hold the request open until the caller gives up. An empty plan reports `unavailable_reason` — `no_active_agreement`, `requested_chains_not_connected`, `peer_unreachable`, `domain_not_shared`, `planner_unavailable` or `federation_unavailable` — instead of an empty error map that read as an authorization verdict. The reasons are aggregate by design and never name a peer.
- **Federated agents appear inside their Access Group.** A federated agent linked to a local Access Group is now shown with the local members, with its authority stated. Federated write remains unavailable: it requires a consensus-bound federation ingress capability.
- **Product-specific bootstrap policy leaves core.** A root-owned provisioning profile now drives `init-fresh-personal-sage` and `check-private-config`. SAGE core no longer carries any one product's home path, Unix account, or unit list. Products that shipped `init-lantern-private` must ship the profile and update their scripts before pinning this release.
- App-v28 remains active and no chain migration is required.
- Container: `ghcr.io/l33tdawg/sage:11.23.25`. SDK 11.23.25.
- ## What's New in v11.23.24
- **Find agents across connected SAGEs in one call.** `sage_find_agent(name="...")` searches this SAGE and caller-authorized contacts on connected SAGEs together by default. Exact name matches rank first in one bounded list. Local matches no longer hide remote matches, and same-named agents keep distinct exact addresses so you can choose the intended recipient.
- Use `scope="local"` to search only this SAGE, or `peer_chain` to select one connected SAGE. If federated discovery cannot be verified, local matches remain available with an explicit incomplete flag. Cached contacts retain their caller-specific authorization checks, and each continuation still reads one bounded peer page.
- MCP descriptions and message guidance now point to the combined lookup. After upgrading, re-list tools or reconnect clients with a cached catalog to load the new parameter and guidance. App-v28 remains active and no chain migration is required.
- Container: `ghcr.io/l33tdawg/sage:11.23.24`. SDK 11.23.24.
- ## What's New in v11.23.23
- **Close reviewed notices without replying.** `sage_message_close(message_id, reason)` records an explicit “closed without reply” outcome for informational or withdrawn messages. Closing retains history and clears pending and unfinished inbox reminders across sessions and restarts. Exact-recipient pending messages need no claim; existing claims remain protected by their current session.
- The close reason stays in recipient history and uses the content vault when enabled. Closures create no reply, read receipt, or sender reply activity. Inbound federated closure is local to the receiving SAGE. REST and both Python clients expose the same action, and startup nudges explain when to use it.
- App-v28 remains active and no chain migration is required. Clients with a cached tool catalog re-list or reconnect to discover the new action.
- Container: `ghcr.io/l33tdawg/sage:11.23.23`. SDK 11.23.23.
- ## What's New in v11.23.22
- **Choose which agents a peer can find.** Federation visibility uses the complete eligible roster instead of general registry entries that could make a partial selection fail. Search by name, provider, or ID, filter Visible/Hidden, and change an individual agent or only the agents matching your filters.
- **Review choices in one place.** Compact rows, Save/Discard, and inline refresh controls keep visibility edits together. Filtered rows stay in place until saving, preserving keyboard focus. The peer's contacts have their own read-only view, while optional memory sharing and access settings are collapsed separately. Agents whose security policy blocks messages remain marked Not accepting.
- Individual and filtered choices stay an exact selection, even when all current agents are selected. **Show all agents** explicitly includes future eligible agents. Visibility grants discovery only; memory access and message delivery keep their existing authorization checks.
- App-v28 remains active and no chain migration is required.
- Container: `ghcr.io/l33tdawg/sage:11.23.22`. SDK 11.23.22.
- ## What's New in v11.23.21
- **Reliable inbox reply catch-up.** The inbox now returns an explicit `reply_watermark_candidate` to save after processing the complete reply range. Its safety flags describe that inbox response and stay fixed while you page. For a truncated reply page, continue until `sage_message_replies` returns `page_truncated=false`, then use the candidate from the original inbox response as the next `reply_since`. An already complete inbox page needs no pager call. This replaces guidance that could send clients through the retained archive repeatedly.
- **Paging keeps its bounds.** Each continuation supplies the next cursor with the same inclusive `since` and page limit. If the retained-reply pointer has no valid head, a returned reply page can still supply a candidate; a response with no valid candidate tells the client to omit `reply_since` on its next poll. Replies at the inclusive boundary remain deduplicated by message ID.
- Clients carrying a tool catalog from before inbox v3 must re-list tools or reconnect to discover the existing `sage_message_claim` and `sage_task_notice_ack` actions. The server already advertises those tools and sends its tool-list change notification during runtime handoff.
- App-v28 remains active and no chain migration is required.
- Container: `ghcr.io/l33tdawg/sage:11.23.21`. SDK 11.23.21.
- ## What's New in v11.23.20
- **Reading the inbox leaves work pending.** `sage_inbox` now inspects messages and task notices without claiming messages, marking notices read, or creating a reply obligation. Agents accept one authorized message with `sage_message_claim(message_id)` and acknowledge one reviewed task notice with `sage_task_notice_ack(notification_id)`. Message and task-notice pages advance independently, so a busy message inbox cannot hide task notices.
- **Agent integrations use the explicit acceptance contract.** The old `sage_messages_receive` MCP tool is removed. Hooks, startup guidance, the Claude channel and the Python SDK use passive inspection; clients must explicitly claim a message before replying. Session ownership, signed federated receipts and recovery of existing claims remain enforced. Reconnect MCP clients after updating so they discover the 36-tool inventory.
- Source builds and release builders move to Go 1.26.9, and both Go modules use `golang.org/x/net` v0.60.0 for the patched standard-library and HTTP/2 dependencies.
- App-v28 remains active and no chain migration is required.
- Container: `ghcr.io/l33tdawg/sage:11.23.20`. SDK 11.23.20.
- ## What's New in v11.23.18
- **SQLite dependency maintenance.** The SQLite driver moves to 1.60.1 with its matching libc dependency. This includes WAL shared-memory read-fault handling that returns an I/O error instead of crashing, plus faster argument binding for statements with many parameters. The embedded SQLite engine remains 3.53.4; Go tooling dependencies are also refreshed.
- **Reranker allocation checks.** The reranker keeps its existing limit of 1,000 results. Its result slice now grows only within the capped selection loop, with no input-sized preallocation. Regression tests cover extreme limits, empty and oversized candidate pools, upstream failures and malformed scores.
- The optional LoCoMo and LongMemEval benchmark environments now pin `datasets==5.0.1`, addressing [GHSA-379c-qx7v-6h59 / CVE-2026-66007](https://github.com/advisories/GHSA-379c-qx7v-6h59). Browser fixture tests use Playwright 1.63.0.
- No consensus execution change, app-version change or chain migration; app-v28 stays active. The experimental, default-off local judge remains pinned to v16, with its runtime, thresholds and published qualification limits unchanged.
- Container: `ghcr.io/l33tdawg/sage:11.23.18`. SDK 11.23.18.
- ## What's New in v11.23.17
- **The optional local judge is now pinned to v16.** On the disclosed frozen 40-item synthetic regression set, the attributed tank-warning example moves from rejection to operator review. All 18 genuine examples avoid rejection: 16 pass and two hold. All 22 negative examples still reject. These results were independently measured on Linux/arm64 with Ollama v0.31.1; they do not establish fresh-holdout accuracy or qualify production installation on every platform.
- Select `SAGE_LOCAL_JUDGE_MODEL=sage-memory-judge:v16` to use the new pin. The memory gate remains experimental and off by default; upgrading does not rewrite an explicit v15 setting. The download uses an immutable Hugging Face revision with separate SHA-256 pins for the downloaded GGUF and Ollama's registered blob. Thresholds, serving template and runtime are unchanged. See the [memory-gate guide](docs/reference/write-gate.md) and [v16 regression results](bench/judge-qualify/results/sage-judge-v16-ollama-0.31.1-go-arm64.json). Thanks to [@ihubanov](https://github.com/ihubanov) for the update.
- No consensus execution change, app-version change or chain migration; app-v28 stays active.
- Container: `ghcr.io/l33tdawg/sage:11.23.17`. SDK 11.23.17.
- ## What's New in v11.23.16
- **Task creation starts at 0.90 across MCP.** When confidence is omitted, `sage_remember(type="task")` now matches `sage_task`; other memory types keep their 0.80 default. Corrections resolve the inherited memory type before choosing the default. Explicit scores, including 0 and 0.80, are preserved; malformed, non-finite and out-of-range scores are rejected. The tool schema describes the conditional defaults without inserting a fixed value that could override correction inheritance.
- **Submission receipts report the score that was signed.** `submitted_confidence` appears on submitted `sage_remember` writes, including corrections and indeterminate outcomes, and on `sage_task` creation, replay and committed-but-unconfirmed receipts. It describes the request, not a later stored or query-time score. Skipped or rejected pre-validation and task-status updates do not report a submitted score.
- Existing memory scores and task idempotency checks remain intact. There is no consensus execution change, app-version change or chain migration; app-v28 stays active and the qualified v15 local judge pin is unchanged.
- Container: `ghcr.io/l33tdawg/sage:11.23.16`. SDK 11.23.16.
- ## What's New in v11.23.15
- **MCP stdio bridges exit when their client process dies.** Inherited pipes can keep a bridge's input open after its client has gone. SAGE now watches the original parent process, cancels its tools and subscriptions on confirmed parent exit, and bounds cleanup even when input or output is blocked. An idle client keeps its bridge.
- **Correction lineage resolves by content hash in CEREBRUM.** The graph and related-memory view find the parent of a correction through bounded metadata lookups on SQLite and PostgreSQL. Legacy exact-ID pointers still work; ambiguous hashes and hidden parents do not expose a lineage edge or memory body.
- **A malformed reranker response preserves the original recall results.** Missing, duplicate or invalid candidate indices and non-finite scores now discard the reranking response as a whole, keeping the existing reciprocal-rank-fusion ordering. The optional reranker remains off by default; its guidance now asks users to compare relevance and latency on their own queries.
- **Federation and message failures explain the next step.** Local storage and target-resolution failures, plus failed requests to known peers, include bounded diagnostics and remedies. Route diagnostics report only attempted candidates and omit credentials, payloads and peer response bodies. Messaging controls also explain that blocking delivery does not hide an agent from discovery.
- The release removes unused memory-transition helpers, expands bounded CI coverage, and documents reproducible retrieval benchmarks and the limits of the public research artifacts. No consensus execution change, app-version change or chain migration; app-v28 remains active. The local judge model stays pinned to the qualified v15 artifact.
- Container: `ghcr.io/l33tdawg/sage:11.23.15`. SDK 11.23.15.
- ## What's New in v11.23.14
- **MCP tool calls stay responsive while another tool waits on HTTP.** Stdio now runs up to 16 tool requests concurrently and reads cancellation notifications immediately. A slow history read can no longer hold later independent tools or the tool registry behind it. Cancellation stops the matching request context; an indeterminate write still requires its normal reconciliation.
- **AMID restores unresolved signer fences before it starts serving.** A private, node-local SQLite ledger preserves identity-only submission intents across process exits. Startup refuses an unreadable or malformed ledger, and a restored fence settles only on chain-proven fate. Disabling the REST validator key also removes the inherited key from ordinary signing paths. A proven fence finishes its durable cleanup before reopening the signer, so a fast next submission cannot lose its new recovery record to the prior cleanup.
- **Block sync rounds quorum-blocking power up correctly.** A validator with power 1 out of 4 no longer leaves block sync early. Actual quorum-blocking power keeps its existing behavior.
- **An optional local judge checks lasting knowledge and its submitted evidence.** Set `SAGE_LOCAL_JUDGE_MODEL=sage-memory-judge:v15` to use SAGE's verified local model through its managed Ollama runtime. It remains experimental and off by default. Judge traffic is restricted to loopback, cloud aliases and mismatched model blobs are refused, and an unavailable judge holds proposals for operator review. Public seed-set qualification on SAGE's pinned runtime passed with external networking blocked; support precision was 97% with one accepted trap, and lasting precision was 100%. See the [memory-gate guide](docs/reference/write-gate.md) and [runtime qualification report](bench/judge-qualify/reports/sage-judge-v15-sage-runtime.md) for configuration and limits. Thanks to [@ihubanov](https://github.com/ihubanov) for the contribution.
- No consensus execution change, app-version change or chain migration.
- Container: `ghcr.io/l33tdawg/sage:11.23.14`. SDK 11.23.14.
- ## What's New in v11.23.13
- **REST submissions keep their acknowledgment through the full write budget.** A memory could commit after the server's response deadline had expired, leaving the caller with a connection error instead of the result. The deadline now accounts for embedding retries, the bounded nonce-lease wait and the consensus commit wait, with time for the response. The default is 285.75 seconds and the combined budget is capped at ten minutes; larger custom settings can still outlast that cap.
- **Vault recovery verifies the key before replacing `vault.key`.** An invalid recovery key is refused before it can overwrite the existing vault key file.
- This patch retains the memory gate shipped in v11.23.11. The unreleased evidence checks, managed local judge and model work are deferred. There is no consensus execution change, app-version change or chain migration. The cancelled v11.23.12 tag remains unchanged.
- Container: `ghcr.io/l33tdawg/sage:11.23.13`. SDK 11.23.13.
- ## What's New in v11.23.11
- **An optional memory-quality gate can hold uncertain memories for review.** Set `SAGE_HUNCH_URL` to enable a background judge for proposed memories, with domain include/exempt settings controlling which memory text reaches the service. Built-in checks still run on every vote, and Settings → Memory gate lets the operator accept or reject held memories. The gate is off by default, supports SQLite stores, and does not change consensus or recall. See the [memory-gate guide](docs/reference/write-gate.md) for configuration and limits. Thanks to [@ihubanov](https://github.com/ihubanov) for the contribution.
- **A provably stale memory vote can release its signer fence.** When a vote's target has already committed, a stale-vote mempool filter can reject every retry before it reaches an indexed block result. SAGE now recognizes a narrow, versioned refusal for complete canonical memories submitted after app-v25 activation. The resolver binds that refusal to the exact signed vote and rechecks the transaction index before reporting its outcome. Ordinary CheckTx 13 errors and historical or incomplete targets keep the fence held.
- **CLI help is inert.** Asking for `serve --help`, `setup --help`, or `mcp --help` returns usage before command dispatch, configuration, or instance locking, without creating home or project files.
- **Inbound federated messages wake their exact local recipient.** Wake allocation commits atomically with message admission and transport deduplication. Duplicate or rolled-back deliveries cannot create extra wakes, and startup catches up existing unfinished inbound work.
- No consensus execution change, transaction-type change, upgrade height, or chain reset. AMID operators must preserve unresolved transaction identity and signed bytes during maintenance: `cmd/amid` does not wire the durable-intent restore hooks used by `sage-gui`, so restarting it is not a fence-recovery proof.
- Container: `ghcr.io/l33tdawg/sage:11.23.11`. SDK 11.23.11.
- ## What's New in v11.23.10
- **A held signing key can no longer park the node's whole write path.** A signer fence refuses every write from its key while it waits for proof of an earlier submission's fate, and that wait was bounded only by the caller's context — which the submit path passed as `context.Background()`, a context that never cancels and carries no deadline. The one goroutine holding the node's single signing lease sat there for as long as the fence stood — one observed node carried handlers parked 122–768 minutes — and every later writer for that key queued behind it on the same size-one lease, including the automatic reconciler whose job is to settle the fence and release it, so the hold could not clear itself. Reads stayed fast and denied writes still failed fast, which is why the incident reached the operator as *writes time out, no error*. `WithNonceLease` now derives a bounded wait (90 s) when the caller supplies no deadline, so a held fence fails retryable instead of parking, the lease is released, and the reconciler is no longer starved by the fence it exists to lift. A caller that supplies its own shorter deadline keeps it.
- **Background work the embedded web handler starts can no longer outlive the store it writes to.** That handler started goroutines with no lifecycle owner, and unowned work that outlived its caller's store touched a closed database and panicked the process — first seen inside this repository's own suite, where one test's projection audit tore down another test's store. Unowned background work is counted now, and a caller that owns the stores drains it with `WaitBackground` before closing them.
- **Build and tooling.** Local `make` builds pin to the host architecture instead of assuming amd64, and a Codex session started in a checkout inherits that checkout's Codex pin from `.codex/config.toml` — the counterpart of the existing `.mcp.json` Claude Code pin, so one workspace can carry both providers' pins. Dependency groups were refreshed.
- No consensus change, no transaction-type change, no upgrade height, and no chain reset.
- Container: `ghcr.io/l33tdawg/sage:11.23.10`. SDK 11.23.10.
- ## What's New in v11.23.9
- **CEREBRUM now shows a held signing key.** A signer fence refuses every write from its key and every coordinated restart while it waits for proof of an earlier submission's fate, and until this release the dashboard said nothing about it — the field report that produced the fence workstream read from the outside as *reads are fine, writes time out, no error*. System Status gains a row that appears only while a key is held: how many keys and how long, the node's own explanation of why the hold is deliberate, and one line per fence naming its resolution. `reconciling` means the identical bytes are still being re-submitted and it clears itself; `waiting on proof` means the signed bytes did not survive the process, so the chain or an operator has to settle it. Each line carries the nonce, how long the key has been held, the attempt count and the last recorded detail.
- **A hold that ends stays visible.** The row above disappears with the fence, which left no way to tell *it lifted while I was reading* from *it never happened*. The last resolution is now kept and rendered — `committed`, `rejected`, `spent`, or resolved without a proof — so a fence that cleared itself is still on screen afterwards.
- **Two details that make the numbers trustworthy.** The nonce crosses the wire as a string: SAGE nonces are nanosecond allocations that exceed JavaScript's safe integer range, and as a JSON number it reached the browser silently rounded, in the one place the operator compares it against the chain. And the panel never suggests restarting to clear a hold — a restart discards the fence and loses the transaction it protects, which is the failure the whole mechanism exists to prevent.
- No consensus change, no transaction-type change, no upgrade height, and no chain reset.
- Container: `ghcr.io/l33tdawg/sage:11.23.9`. SDK 11.23.9.
- ## What's New in v11.23.8
- **A node stops manufacturing signer fences on an ordinary quit.** Since the fence landed, every coordinated restart has drained signing before it committed, so its teardown could not sever a broadcast mid-flight. A plain signal or a serve error had no such drain: the HTTP force-close could catch a submission, raise an indeterminate outcome, write a durable fence record, and cost that payload at the next start — the fence can only lift on a proof, and a live one whose re-submission is refused by anything other than the nonce gate has no proof to reach. The ordinary exit now drains the same way the restart does: signing is quiesced, in-flight submissions get a bounded five-second window to finish, and only then do the listeners close. Signing is deliberately not resumed, because the process is leaving; an operator-ordered exit is never vetoed by the drain; and a submission that cannot finish in the window fails closed onto the durable record and the restored fence.
- **`sage-gui fence abandon` works on a node that keeps a peer.** The credential-free operator exit added in 11.23.6 applies the same evidence gate as the daemon's abandon route, including its second acknowledgement for connected peers — a peer is a route the abandoned bytes could still take back into this node's mempool. The CLI had no way to carry that acknowledgement, so on a federated desktop node or a validator with a persistent peer it could only ever refuse and point at a field it had no way to set. `--peer-redelivery-acknowledged` now carries it, `fence list` names the requirement when peers are connected, and every unproven record states the restart step: a running daemon keeps holding the key until it restarts, and the durable record is what the next boot restores from.
- No consensus change, no transaction-type change, no upgrade height, and no chain reset.
- Container: `ghcr.io/l33tdawg/sage:11.23.8`. SDK 11.23.8.
- ## What's New in v11.23.7
- **A node that has activated app-v28 can install its own updates again.** The signed update flow takes a pre-upgrade recovery snapshot and proves it before it touches the installed app: the manifest carries the AppHash the running chain committed, and the proof restores the Badger backup and re-derives that digest from the restored bytes. Since app-v28 the committed AppHash is the public-memory composite commitment — the app-v13 digest of the state WITHOUT the public-memory index nodes, composed with the sparse index root — and the proof only knew the three earlier eras. Every app-v28 node therefore refused its own recovery snapshot, and the field report was exactly this shape: `Failed to install signed app update: verify pre-upgrade snapshot: ... AppHash mismatch under every hash rule (legacy/app-v12/app-v13)`, with the update stuck on the snapshot step and no way forward from inside the app.
- **What now happens:** the composite joins the candidate set, read through the same `internal/store` implementation the commit path uses instead of a second copy of the rule — the state-sync provider verification path already went stale exactly that way once, refusing every v28 provider while every pre-v28 chain stayed green. A pre-v28 state carries no public-memory commitment, so the composite is reported as not-applicable there and the three older candidates decide alone. The mismatch message now names the rules that were actually tried.
- **If you are reading this from an app-v28 node on 11.23.6 or earlier, read this part.** The gate that just failed runs inside the binary you have installed, so that binary cannot install this release either — and the same gate vetoes a version-changing restart. Installing 11.23.7 once by hand is the path out: quit SAGE, drag `SAGE.app` from the DMG into `/Applications`, relaunch. Every update after that one works from inside the app again.
- No consensus change, no transaction-type change, no upgrade height, and no chain reset.
- Container: `ghcr.io/l33tdawg/sage:11.23.7`. SDK 11.23.7.
- ## What's New in v11.23.6
- **A fence on a quiet chain settles itself, and the operator has a way in when it cannot.** SAGE chains are idle by design: since app-v12 every node sets `create_empty_blocks=false`, so a block is minted exactly when a signed transaction enters the mempool and the chain sits still otherwise. A fence restored from durable intent refuses to sign, and its signed bytes did not survive the process — so on a chain that was already quiet when the fence was raised, the fence was holding the only thing that could produce the proof it was waiting for. No transaction meant no block; no block meant no committed hash and no advanced committed nonce. The key was held forever, every write and every cleanup on that node was refused, and the field report was exactly this shape on a single-validator personal node.
- **What now happens:** when the node is caught up, has no peer and has seen none while this fence was held, holds no mempool copy of the transaction, sees no committed fate for its hash and holds an unspent allocation, the node settles the fence itself, records `fence_abandoned` and the full evidence, reserves the abandoned allocation so the next transaction cannot reuse it, and lets the next write mint the block that wakes the chain. TWO EVIDENCE SETS REACH THAT DECISION and the log names which one did: `mode=automatic_unprovable` is the original startup resolution, and `mode=automatic_quiescent` is the rule added here for a chain that has minted nothing since the fence was raised — the first now succeeds where it previously could not, because the reader defects below were what stopped it reaching its gates.
- **What still holds the fence:** a tip that has minted since the fence was raised, any connected peer, a peer seen under this fence, a mempool that holds the transaction — that is a chain with something to mint and the fence is what stops it, so it stays an operator decision — a node still catching up, a tip that cannot be read, a live fence whose exact bytes still exist, and any record without a nonce.
- **Every outcome of the automatic route is now visible.** Its refusal reason reaches the fence's `last_detail`, and so does a FAULT — the fault branch was previously dropped silently, which made a node whose self-heal could not read its own evidence look identical to one that was merely waiting. A field report read that as "the automatic route never ran".
- **The operator has a real entry.** `sage-gui fence list` prints every recorded fence with its signer, transaction, nonce and age, and says whether the chain can already settle it. `sage-gui fence abandon --signer <key> --reason <why> --acknowledge-payload-loss` retires one record from the node host through the same evidence gate the daemon's operator route applies — no credential, no browser, and it says plainly that a running daemon keeps its in-process fence until it restarts. This closes a field gap: the dashboard had no control for this action, and an HTTP MCP bearer token is not accepted by the operator gate, so the only local entry was a browser console.
- No consensus change, no transaction-type change, no upgrade height, and no chain reset.
- Container: `ghcr.io/l33tdawg/sage:11.23.6`. SDK 11.23.6.
- ## What's New in v11.23.4
- **A fence on a quiet chain settles itself.** SAGE chains are idle by design: since app-v12 every node sets `create_empty_blocks=false`, so a block is minted exactly when a signed transaction enters the mempool and the chain sits still otherwise. A fence restored from durable intent refuses to sign, and its signed bytes did not survive the process — so on a chain that was already quiet when the fence was raised, the fence was holding the only thing that could produce the proof it was waiting for. No transaction meant no block; no block meant no committed hash and no advanced committed nonce. The key was held forever, every write and every cleanup on that node was refused, and on a single-validator personal node the hold had no exit at all — the operator route needed a credential the operator could not present.
- **What now happens:** when the node is caught up, has no peer and has seen none while this fence was held, holds no mempool copy of the transaction, sees no committed fate for its hash, holds an unspent allocation, and the chain's tip was minted before this fence was raised, the node settles the fence itself, records the decision as `fence_abandoned` with `mode=automatic_quiescent` and the full evidence (including the tip height and time), reserves the abandoned allocation so the next transaction cannot reuse it, and lets the next write mint the block that wakes the chain.
- **What still holds the fence:** a tip that has minted since the fence was raised (that chain can still speak to these bytes), any connected peer, a peer seen under this fence, a mempool that holds the transaction — that is a chain with something to mint and the fence is what stops it, so it stays an operator decision — a node still catching up, a tip that cannot be read, a live fence whose exact bytes still exist, and any record without a nonce.
- No consensus change, no transaction-type change, no upgrade height, and no chain reset.
- Container: `ghcr.io/l33tdawg/sage:11.23.4`. SDK 11.23.4.
- ## What's New in v11.23.3
- **The fence fixes now reach the nodes that keep a peer.** v11.23.3 could prove a restored fence's fate and settle the shape no proof can reach — but only on a node that had never seen a peer since it started, and its operator abandon route refused outright whenever any peer was connected. A federated desktop node, or any validator with a persistent peer, therefore sat behind a fence that no proof could settle with **both** recovery routes closed: writes refused, updates vetoed, indefinitely. That is the report this release answers.
- **The peer observation is anchored to the fence, not to the process.** A sighting from an earlier outage — a peer that connected while the node was starting, a peer gone for hours — can no longer switch self-healing off for every fence raised afterwards. What still holds is the honest rule: the automatic route refuses while a peer is connected, or was seen while *this* fence was held, because a peer is how a transaction gets delivered back.
- **The operator abandon route now says what it needs.** It reads the live peer count, still records it with the decision, and requires a second, explicit acknowledgement — `peer_redelivery_acknowledged` — when peers are connected. The operator can see the topology (whether that peer was running when the submission went out, whether it ever held the bytes); the node cannot, so it states the route it cannot rule out instead of refusing by construction.
- **The health surface says HOW a fence ends.** Each held fence now reports a resolution class: `reconciling` means the node still holds the exact signed bytes and is re-submitting them until consensus answers, so it clears itself; `proof_or_operator` means the fence was restored from durable intent and its signed bytes did not survive, so only a chain-read proof or an explicit operator abandon will lift it. The block's explanation is rendered from that distinction instead of promising self-healing for every fence, and the automatic route's own refusal reason (still catching up / peers connected / a peer seen under this fence) is recorded with the fence rather than computed and dropped.
- **Agents can read it directly.** The MCP surface gains a read-only `sage_node_health` tool (the 35th): it forwards the node's `signer_fences` block and renders the guidance from the resolution class, and says "not knowable from here" rather than guessing on a node too old to report one. A write refused with `503 Signing key temporarily held` can now be diagnosed by the agent that hit it, without an operator shell.
- No consensus change, no transaction-type change, no upgrade height, and no chain reset: this decides when a key may sign again, not what the chain accepts.
- Container: `ghcr.io/l33tdawg/sage:11.23.3`. SDK 11.23.3.
- ## What's New in v11.23.3
- **A held signing key can no longer strand a node, and a write that hits one says so.** The signer fence refuses to let a key sign anything new while an earlier transaction's fate is unproven — that part is deliberate and unchanged. What was wrong was everything around a fence that got restored after a restart: its signed bytes are gone, so re-submission cannot prove anything, and the node had no other way to settle it. It held the key, refused every coordinated restart (which is every in-app update), and the only exits were an operator POST that needed a proof the chain did not have, or hand-editing the database. Users hit it as an upgrade that could not be installed and, on the nodes that did restart, as writes that timed out with no error while reads stayed fine.
- **A restored fence now proves what it can, and settles what it cannot.** On the first boot of this release the node re-reads the chain for the two proofs it accepts — the recorded transaction hash found in a committed block, or the signer's committed nonce having reached the fenced allocation — on the same retry schedule the live reconciler uses, and lifts the fence the moment either exists. For the shape no proof can ever settle (the transaction never committed, and the bytes died with the process that sent them) the node resolves the fence itself once the evidence is unambiguous: it is caught up, it has seen no peer this run, nothing is queued in its mempool, the recorded hash is in no block, and the allocation is unspent. That decision is recorded as a `fence_abandoned` event with `mode=automatic_unprovable` and the full evidence, and the abandoned nonce is reserved so the next transaction cannot reuse it. A node that has talked to a peer keeps its fence — there the transaction can still come back, and only a proof or an operator may lift it.
- **The restart veto now asks the right question.** It used to refuse any coordinated restart while a fence was held, on the reasoning that a restart discards the only record of a possibly in-flight transaction. Since durable intent landed, that record is on disk and is re-raised at the next start, so the veto now refuses only when it cannot confirm the record survives (an unwired, unreadable or missing intent row — it fails closed). Refusing blanket-wide was itself the bug: a fenced node would not take the restart that installs the release carrying the fence's own proof reader and recovery.
- **A fenced write is refused immediately instead of hanging.** The lease's fence wait blocks until the caller's deadline, so an agent writing to a fenced node saw a bare timeout. Request-serving paths now check first and answer `503` with `Retry-After`, naming the transaction the key is held on and stating that nothing was signed or sent.
- **Already stuck on v11.23.2? Replace the app.** A node that is fenced right now refuses the in-app restart that would install this release, so the recovery is the app itself: drag the new SAGE into `Applications`, replacing the old copy, then quit and reopen it. The first boot of v11.23.3 resolves the fence on the evidence above and writes work again — no terminal, no command to run. The proof route (`POST /v1/dashboard/signer-fence/lift`) still exists for anyone whose key can be proven, and the operator abandon route remains for fleets that keep their fence because they have peers.
- No consensus change, no transaction-type change, no upgrade height, and no chain reset: this decides when a key may sign again, not what the chain accepts.
- Container: `ghcr.io/l33tdawg/sage:11.23.2`. SDK 11.23.2.
- ## What's New in v11.23.2
- **A chain whose public corpus predates app-v28 can open the fork.** The public-memory stage is built by `BuildPublicMemoryMigration`, which refused to produce a leaf for any `PUBLIC=0` record it could not canonically encode — and a real chain carried 53 legacy records whose canonical content hash had been erased by a historical lifecycle transition. Because the stage is prepared outside the consensus transaction, that refusal aborted the activation block on **every** replay: CometBFT re-entered "replay last block using real app" and the node could not start at all, so `upgrade cancel` could not help either — it is itself a consensus transaction. Those records are now quarantined out of the committed public set instead of failing the build, exactly as the co-commit tombstone index already treats a record whose decoded hash is not 32 bytes, and a record joins the set in the block that re-anchors its hash.
- **Narrow by design.** Only a record accepted before app-v25 lacks a submission-height marker, and only those could have had their hash erased by a legacy lifecycle transition, so a missing hash on a record born under app-v25 or later is still a hard inconsistency that refuses the build. Nothing about the commitment itself changes: this decides whether an activation succeeds, not what the fork commits.
- No transaction-type change, no upgrade height, and no chain reset.
- Container: `ghcr.io/l33tdawg/sage:11.23.2`. SDK 11.23.2.
- ## What's New in v11.23.1
- **An amid-only fleet can set an agent's enrollment clearance.** A validator fleet with no CEREBRUM SPA could not raise an existing agent's clearance: the only producer of `TxTypeAgentRoleChange` is the dashboard policy route, the legacy PATCH route is retired post-app-v23, and `amid` served neither. `amid` now mounts exactly two dashboard routes on its own REST listener — `GET /v1/dashboard/network/access` and `PUT /v1/dashboard/network/access/agents/{id}/policy` — with the same handlers and the same operator gate CEREBRUM serves, so the transaction is identical. The caller signs the exact request as the current Root; the node's configured broker key (`--cerebrum-root-key-file` / `SAGE_CEREBRUM_ROOT_KEY_FILE`) is that credential, and a node without it answers `root_key_unavailable` instead of degrading open.
- **Enrollment clearance is the one the memory-write gate reads.** Membership clearance is a different record and never satisfies the gate that compares a submission's classification against the agent's *enrollment* clearance; this is the surface that writes it, with the role and enrollment revisions the read route exposes.
- No transaction-type change, no consensus change, and no chain reset. A patch release inside the 11.23 line: the shipped native shell already admits v11.23 daemons, so no shell range moves.
- Container: `ghcr.io/l33tdawg/sage:11.23.1`. SDK 11.23.1.
- ## What's New in v11.23.0
- **App-v28 activates.** `maxSupportedAppVersion` moves 27 → 28 and converges with the compiled ceiling, so the gate v11.22.0 shipped dormant becomes an automatic rung: a personal node now advances its own chain across the seam on upgrade with no governance ceremony, the same path every earlier rung took. What activates is the sparse public-memory Merkle commitment over committed `PUBLIC=0` records — AppHash-covered through a composite rule that hashes the legacy tree without the index nodes and composes it with the index root — and the co-commit tombstone rule, now enforced by the consensus path behind a content-hash reverse index maintained by every memory write and backfilled at activation.
- **The state-sync item that blocked it is fixed, and the contract's evidence is complete.** A v28 provider used to die on its state-sync serving boot: the verification family recomputed the pre-v28 AppHash rule unconditionally, so the composite root could never match, the process exited with `persisted AppHash does not match Badger state`, and the caller waited on a Comet RPC that never became ready. The rule is now selected in one function shared by the commit path and the verification path, so the two cannot disagree about which rule is in force. `TestAppHashDeterminism_AppV28Activation` walks a fresh four-validator devnet app-v2 → app-v28 one rung at a time with byte-identical AppHash at H-1/H/H+1 of every seam; both Consensus Fault Gates pass on this change; and the real-process state-sync gate drives its provider through app-v28 (`TARGET_APP_VERSION=28`), so a pristine receiver restores from the provider snapshot and both sides report exact app-v28 state with converging AppHash. The gate's receiver pre-publication SIGKILL and provider SIGKILL phases, plus the replay family that pins historical blocks to their original app versions, cover restart and replay equivalence across H.
- **The native shell rides this release.** A minor bump is the release that widens the shipped shell's SSCP compatibility range, which now admits v11.23 daemons — so fixes after this one ship as patch releases under the same shell.
- No chain reset and no transaction-type change; historical blocks keep replaying under their original app versions.
- Container: `ghcr.io/l33tdawg/sage:11.23.0`. SDK 11.23.0.
- ## What's New in v11.22.1
- **App-v28 stays dormant in this release.** v11.22.0 shipped the public-memory commitment and the consensus-side co-commit tombstone rule as one compiled gate, with the auto-vote ceiling deliberately held at 27 until its evidence existed. That evidence is nearly complete — the four-validator determinism ladder crosses every seam to app-v28 with byte-identical AppHash, and the upgrade gate drives the whole ladder with auto-votes — but the contract's last item, a promoted node surviving state-sync and restore, currently fails: a v28 node restarted by the real-process state-sync gate comes back, serves, and then stops answering. The ceiling bump ships in the release that turns that green, so app-v27 remains the ceiling here and the deliberate path (propose plus explicit votes) is unchanged.
- **The Federation page now leads with your connections.** Managing a link used to mean scrolling past a status rail, the master switch, a network-name editor, a connectome for every agent, an always-open pairing wizard and only then the connections themselves, and per-agent discovery hid behind a Save button inside an expanded panel. The page opens on Your trusted SAGEs instead. Each connection row states its own discovery posture — all agents visible, N agents visible, or no agents visible — from one bounded read per link, so the row answers without expanding. The connectome and sharing groups move into collapsed Explore agents and Sharing groups sections at the bottom, and the pairing wizard appears only when there are no connections or when Connect a SAGE is used.
- **Agent visibility is a switch, not a form.** Every eligible agent on a connection's roster carries a Visible/Not-visible switch that saves immediately under the connection's revision-bound agreement. The switch works on the full roster, so hidden agents never vanish from the operator's list, and Show all agents / Hide all agents move the whole roster at once. The Save-then-Saved form is gone, and copy-address is demoted to a quiet secondary action on peer cards.
- **The SDK can set an agent's enrollment clearance.** `set_agent_access_policy(agent_id, role, profile, clearance, capabilities=0, home_domain=None)` writes the atomic app-v23 policy endpoint, and `get_access_state()` reads the consensus-authoritative snapshot back, so a script verifies the write landed instead of inferring it. This closes a gap that reads as a bug: the memory-write gate compares a submission's classification against the agent's *enrollment* clearance, not its organization or department membership clearance, so an operator who granted clearance through membership saw every classification ≥ 2 write refused while `get_profile()` still reported clearance 1.
- **CEREBRUM's App version panel renders on every node.** The panel (chain rung, both ceilings, the Propose button) was nested behind the governance-scope list, so it never rendered on a personal node — scope records only exist once a `scope_action` commits, and most nodes have none. It now renders on its own, and only the scope cards stay gated.
- No consensus change and no chain reset. `maxSupportedAppVersion` stays 27.
- Container: `ghcr.io/l33tdawg/sage:11.22.1`. SDK 11.22.1.
- ## What's New in v11.22.0
- **App-v28 ships compiled and dormant, on purpose.** Two consensus-visible changes now exist behind one gate. The sparse public-memory Merkle index over committed `PUBLIC=0` records becomes AppHash-covered at the activation height, through a composite rule that hashes the legacy tree without the index nodes and composes it with the index root. The co-commit tombstone rule stops being a check at the local REST submission boundary and becomes a rule the consensus path enforces. Neither one is active: `maxSupportedAppVersion` stays 27, so every node's upgrade auto-voter abstains on v28 and a personal node cannot advance itself into the fork. Activation waits for the evidence the contract names — byte-identical AppHash across the seam on a four-validator devnet, both Consensus Fault Gates, a promoted node surviving state-sync and restore, and replay equivalence — and ships in the release that carries it. An explicitly proposed, quorum-approved plan can still activate it; nothing does so on its own.
- **The tombstone rule is a consensus rule now.** A co-commit never consults the voter — block inclusion is decisive — so the content-hash dedup that keeps a rejected memory's exact bytes out of the store never ran on that path, and a directly broadcast envelope never met the REST guard at all. The predicate needs data consensus state did not carry: `memory:<id>` is a content hash plus status, so "did these exact bytes already leave `proposed` under a different id" had no reverse lookup. The fork adds one — an entry per content hash and id that has left proposed — maintained by every memory write, backfilled from existing records at activation, and consulted from H+1 with the candidate's own id excluded so an idempotent re-send is decided by its own record.
- **The binary now states two ceilings instead of one.** What it can execute (app-v28, compiled) and what it will auto-vote (app-v27) are different numbers while a gate awaits its evidence, and the surfaces say which is which: `upgrade status` and `upgrade preflight` print both, the version banner and full-backup stamp follow the compiled ceiling, and state sync accepts a restore up to it, so a promoted node can be rebuilt from a snapshot. The acceptance gate and the authorization ceiling moved with them, and the invariant that used to require all three numbers to be equal now states what each one means.
- **Upgrades can be proposed and voted on from CEREBRUM, and voted on from the terminal.** The Governance view gains an App version panel — the chain's rung, both ceilings, the pending plan, the active ballot, a Propose button for the next rung — and `sage-gui upgrade vote` casts an explicit accept, reject or abstain. That path matters because a dormant gate is designed so nothing auto-votes: reaching quorum is a deliberate act by validators, which is what the panel and the command exist for. The generic governance-propose route still refuses `OpUpgrade` by design; the dashboard speaks the dedicated `UpgradePropose` transaction instead.
- No chain reset, no transaction-type change, and historical blocks keep replaying under their original app versions. app-v27 remains the ceiling until v11.22.0's dormant gate gets its evidence.
- Container: `ghcr.io/l33tdawg/sage:11.22.0`. SDK 11.22.0.
- ## What's New in v11.21.0
- **The 11.21 line opens, and the shell that admits it ships with it.** The daemon is the v11.20.5 build: a peer whose address moved repairs its own route, a flapping peer's windows are spent on the backlog, and recall names the confidence floor that filtered a result instead of returning an empty answer. What is new is the line itself. The SSCP compatibility range lives in the shipped native shell, not in the daemon, so a minor bump is the release that has to widen it: the shell now accepts v11.10 through v11.21 daemons, which is what lets the fixes after this one ship as patch releases instead of a rebuilt shell each time. If you run the daemon and the desktop app as separate installs, update both — an 11.21 daemon under the 11.20.5 shell is refused control by design, and that refusal is the gate doing its job rather than a fault.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.21.0`. SDK 11.21.0.
- ## What's New in v11.20.5
- **A peer whose address moved repairs itself instead of waiting for a human.** The R2 fix let a P2P-only agreement run the authenticated route exchange across trust generations, because withholding the route fallback left it no transport at all. The same assumption fails for an agreement paired with a *concrete* endpoint once that host moves: the address is real, so nothing looks unroutable, but every request dials a machine that no longer answers while the peer's own traffic keeps arriving — the asymmetry operators report as "they can reach us, we cannot reach them". Withholding the fallback there also blocked the exchange, which is the only thing that can replace the stale snapshot, so the pair could never recover without re-pairing. The exemption is now about the path rather than the agreement shape: the exchange may use a stale snapshot as an authenticated bootstrap hint for both, while every other request still refuses a cross-generation route, and the persisted result is revalidated against the exact agreement and binding before it is written. A moved host also no longer reads as an offline one: the failure carries the trust-generation recovery code, so the operator's next move is a route repair rather than a network investigation.
- **A window of reachability is spent on the backlog, not on one message.** A peer that flaps hands out short windows, and the drain only attempts rows whose backoff has expired — so a fresh event, due immediately on its first attempt, consumed the window while older rows slept through it. That is exactly the shape of a message created at 21:15 delivering while messages from 21:10 and 21:11 stayed queued. A successful delivery now proves the peer reachable and makes the rest of *that peer's* backlog due at once (attempt counts and last errors untouched — only the sleep is cleared), and a drain pass covers sixteen rows rather than four, with concurrency unchanged.
- **Recall no longer hides results behind the confidence floor without saying so.** A memory reachable by tag was invisible to semantic recall because the node's floor (85) sat above the confidence its records were written with (0.80): the floor is applied before ranking, so no query can compensate, and the response said nothing — the whole observation tier is unreachable on a node tuned that way. Recall now reports the floor it ran with, how many candidates the floor removed, and a one-line note naming the remedy and the tiers a floor above 0.80 or 0.60 hides; the REST envelope carries the same facts under `filtered` and the `X-SAGE-Filter-Applied` header, and the settings surface warns where the value is read and saved. A floor that removed nothing is disclosed too, because that is what lets an empty result be trusted.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.20.5`. SDK 11.20.5.
- ## What's New in v11.20.4
- **A signer fence now survives the process that raised it.** The fence is in-process state, and its own documentation named the hole: a restart, crash or SIGKILL discarded it, after which the nonce allocator re-seeded each key from the highest *committed* nonce — below the abandoned one by definition, because "unresolved" is what unresolved means — and the next action signed into that gap. The abandoned transaction was refused Code 4 when it finally landed, and the loss was untraceable: an operator saw an unrelated later action fail as a replay. Every submission is now shadowed by a durable record written at the last boundary before the bytes reach the transport, retired only on a proven fate, and re-raised as a fence at startup — so a node that was killed mid-submission comes back **refusing to sign that key** instead of re-seeding past it. Measured against a real cluster: two validators held fences for 13 days while their transaction sat in neither chain nor mempool, and their restarts bought exactly one signature each because the discarded fence was the only record of it.
- **A nonce that is provably dead now has an exit.** The fence's rule is that only proven fate lifts it, which left one shape it could not resolve on its own: a submission whose fate was never observed and whose signed bytes did not survive the process. `POST /v1/dashboard/signer-fence/lift` (behind the CEREBRUM operator gate) accepts two proofs and nothing weaker — the exact transaction found in a committed block, or supersession, meaning a higher nonce for that signer has already committed, which makes the fenced allocation permanently uncommittable under the consensus nonce rule. Both proofs are read by the node rather than asserted by the caller, and a superseded lift records that the fenced transaction's payload is permanently lost. A lookup miss stays unproven: CometBFT indexes a transaction only once it is in a block, so a mempool-resident transaction answers not-found exactly as it does one second before it commits.
- **What the record deliberately does not carry.** Not the signed bytes. Those routinely hold memory content that must not be copied into a plaintext table, so a restored fence resolves by proven fate instead of by re-submission. And a crash between the record and the wire holds a key that may have nothing in flight — the safe direction, resolved through the same proof path.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.20.4`. SDK 11.20.4.
- ## What's New in v11.20.3
- **A peer's "too large" answer no longer kills the message.** The federated outbox classified `413` alongside the 4xx statuses that mean the peer understood the request and refused the bytes, so a single refusal marked the transport event `failed` and the canonical message with it: the row is never scanned again, and a durable-until-handled message carries an expiry a century out that never relieves it. That verdict is wrong for this status. A peer's per-route body cap is a build-time constant that moves when the peer upgrades, and the refusal is frequently not about size at all — on 2026-09-15 a message was refused as too large while its signed body sat 2.6 KB *under* the route's 16 KiB cap, and a *larger* message to the same peer was accepted unchanged minutes later. `413` now retries on an hourly floor, like the other capability-shaped status, so the event stays pending and delivers once the peer can take it.
- **The listener stopped calling every body it could not read "too large".** The federation gate read the request body and answered `413` for any error, which merged a genuine over-cap body with a truncated upload, a mid-body disconnect and a stream reset — and the sender's terminal `413` rule turned that mislabel into permanent loss. Only a real `*http.MaxBytesError` is `413` now; a body this node could not read is answered as a read failure, which stays retryable, and logged with its underlying cause.
- **A delivery failure is visible in the log.** The transport worker logged only when *recording* a failure failed, so an event could die with nothing in the log to say why. Every failed attempt now carries the event, the peer, the kind, the attempt count, the verdict and the retry delay.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.20.3`. SDK 11.20.3.
- ## What's New in v11.20.2
- **A submission whose outcome the node could not observe is now reported as exactly that, instead of as a failure.** Every REST submit waits for `broadcast_tx_commit`, and that wait can expire before the block lands — on a loaded cluster the transaction then commits seconds later, while the caller has already been told `500 Broadcast error`, indistinguishable from a genuine internal fault. That was worse than unhelpful: a caller retrying "on error" re-signs, so one write can be applied twice. The endpoint now answers `202` with `"status":"indeterminate"`, the exact `tx_hash` of the bytes that went on the wire, the allocated `nonce`, and `"retryable":false`, while the node's signer nonce fence keeps reconciling the real fate.
- **Definitive outcomes keep their verdicts.** A CheckTx or FinalizeBlock rejection still returns the status it always did, and a full mempool still returns `429` with `Retry-After` — nothing was admitted, so there is nothing in flight to chase.
- **Generated testnets stop inheriting the wait that causes it.** `deploy/init-testnet.sh` now writes `timeout_broadcast_tx_commit` explicitly (45s) rather than leaving CometBFT's 10s default, and keeps it strictly below SAGE's own client-side wait (`SAGE_TX_COMMIT_TIMEOUT_MS`, 60s) so the node — which knows whether it admitted the bytes and can name the transaction hash — is always the party that answers.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.20.2`. SDK 11.20.2.
- ## What's New in v11.20.1
- **Federated replies are deliverable for a week, not a day.** The window a reply stays admissible, and the deadline its retained outbox event is retried until, move from 24 hours to seven days (`federation.PipeEventResultLifetime`). A destination re-derives that window from the signed proof, still admits the legacy 24-hour window, and a destination that predates the longer one is answered by one downgraded retry at the old window instead of a terminal failure — so replies keep flowing while peers upgrade at their own pace. Receipt evidence about a message keeps its own separate 24-hour grace.
- **Replies can no longer be permanently lost to a local retention re-stamp.** The startup migration that extends durable canonical sends matched every pending `msg-%` outbox row, including the receiver-local `msg-fed-…` id of an imported message — whose outbox row is a reply. It re-stamped those replies to a +100-year lifetime, which the destination refuses as an invalid proof, and because the same column is the retry deadline it also removed the give-up path, so the reply retried until it happened to reach the peer and collect the permanent 400. The rescue is now scoped to sends, stamps the exact durable sentinel (`+36500 days`, not SQLite's calendar `+100 years`), repairs rows an earlier build already extended, and reply envelopes are built from the signed proof so local retention state can never reach the wire.
- **A refused proof now says why.** The destination logged nothing when it refused a proof, and the sender only recorded the destination's single opaque `invalid pipeline agent proof` refusal, which is how ten historical reply failures stayed unattributable. The destination now logs the exact reason and the sender checks its own reply envelope against that same rule before pushing.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.20.1`. SDK 11.20.1.
- ## What's New in v11.20.0
- **An agent's working state can now be stored encrypted on the node.** Two new surfaces are reachable only from inside the app-v23 pipeline agent boundary, and both refuse to run without the Synaptic Ledger vault: `PUT`/`GET /v1/private-media/{uuid}` stores immutable JPEG originals with ciphertext-only rows, per-caller actor isolation, quota enforcement and a startup disk-floor probe, and `PUT`/`GET /v1/workflows[/{uuid}]` gives an agent an encrypted, actor-bound journal for long-running work with compare-and-swap revisions, strict argument bounds and an opt-out conversation guard. Neither surface can be reached for another agent's rows, and neither writes a plaintext copy to the database or its WAL.
- **You can now prove whether message storage is encrypted.** `GET /v1/messages/storage` reports the honest storage posture of this node, and `POST /v1/messages` accepts a strict signed `require_encrypted_storage` boolean: an agent that must not be stored in the clear now gets a `503` instead of a silent downgrade, and a malformed or unsigned value is rejected rather than ignored. The authenticated request-body limit became route-aware for exactly one route: a canonical-UUID private-media `PUT` gets one extra MiB, everything else keeps the 1 MiB ceiling.
- **Local durability is no longer taken on faith.** SQLite opens with `synchronous=FULL` in both DSN and `PRAGMA` form and the node verifies `journal_mode` and `synchronous` at boot, refusing to serve when the durability posture is not provable. Vault publication is atomic in the same vein: attaching a vault and marking encryption required can no longer be observed separately, so an unlock cannot leave a window where a write is accepted against a store that does not yet require encryption.
- **Managed appliance bring-up, with no product names in core.** `sage-gui init-fresh-personal-sage --profile <path> --unit <id> --owner-approved-companion-bootstrap` creates a fresh-only personal identity from a root-owned, mode-0600 provisioning profile. It refuses an existing or mismatched node rather than reusing it, takes its companion-key bootstrap explicitly, and never installs services or enables public enrollment. A profile that sets `private_listeners: true` makes a missing config an explicit error rather than a default, and the policy is re-checked when the YAML is loaded so an edit cannot silently weaken it. The product that ships a profile owns its home path, Unix account, unit ids and artifact filenames; SAGE core knows none of them.
- **A public-memory Merkle index ships dormant, and no fork is opened.** The sparse SHA-256 index over committed `PUBLIC=0` records, its migration builder and its stage/promote path are in the tree with their tests, and no production code calls any of them. Staged rows live under a local namespace that is excluded from the AppHash; promotion is what writes into AppHash-covered state, it is explicitly named for app-v28, and it is not reachable from a running node. Read that as preparation, not as activation.
- **Federation: you decide which of your agents the other side can find.** A trusted link advertised every eligible ordinary agent to the peer, which is convenient with one agent and confusing with a dozen — the other operator sees names they do not recognise and sends work to the wrong one. Each connection now carries an explicit discovery policy: **All agents** (the default), **Only the ones I pick**, or **None**. Ticking one agent narrows the connection to exactly that agent, ticking more adds them, and **Save discovery policy** commits it under the same revision-bound agreement the rest of federation uses. It governs listing and exact-name search only: it grants no memory Read and authorises no delivery, and an agent that still refuses federated delivery stays visible as **Not accepting** by design so the peer is never promised a route it cannot use.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.20.0`. SDK 11.20.0.
- ## What's New in v11.19.22
- **The Go build floor moves to patched 1.26.8.** Both modules now declare `go 1.26.8`, up from `1.25.13`, and every Go container builder moved with them: `Dockerfile`, `deploy/Dockerfile.abci`, `deploy/Dockerfile.node`, both federation-acceptance Dockerfiles and `deploy/init-testnet.sh`. Building from source now requires Go 1.26.8 or later.
- This is not a fix for a hole you have. v11.19.21 and everything before it were built with Go 1.25.13, and that toolchain scans clean on its own standard library. It is a deliberate move forward: the dependency group below requires Go 1.26, and the bare `1.26.0` those tools would otherwise have pinned is precisely the version `govulncheck` reports 26 reachable standard-library advisories against — among them `net/url` (GO-2026-6218), `html/template` (GO-2026-6091), `crypto/tls` (GO-2026-6090, GO-2026-5856), `net/http` (GO-2026-6089, GO-2026-5026), `encoding/xml` (GO-2026-6088), `encoding/asn1` (GO-2026-5972), `net/textproto` (GO-2026-5039) and `crypto/x509` (GO-2026-5037). 1.26.6 is the minimum fix for those; 1.26.8 is the newest patch of the line, and on it the vulnerability gate reports no reachable vulnerabilities in either module.
- **Dependencies refreshed.** `github.com/jackc/pgx/v5` v5.11.0, `github.com/klauspost/compress` v1.20.0, `golang.org/x/crypto` v0.57.0, `golang.org/x/sync` v0.23.0, `golang.org/x/sys` v0.48.0, `golang.org/x/tools` v0.50.0 and `modernc.org/sqlite` v1.58.0, plus the `x/net`, `x/mod`, `x/text` and `x/telemetry` indirects. The SQLite driver moves to SQLite 3.53.4, which carries upstream's own journal-rollback fix — the reason the local super-journal patch existed — so that patch retires with no change to recovery behaviour. The pgx bump adds `TypeMap` to the `pgx.Rows` interface, so the store tests move from `pgxmock/v4` to `pgxmock/v5`; that is a test-only import change with no runtime effect.
- Also in this release: `golang.org/x/crypto` still carries GO-2026-5932 at v0.57.0, its newest release. It is in the module graph and is not reachable from SAGE code; the gate reports it as uncalled rather than failing.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.19.22`. SDK 11.19.22.
- ## What's New in v11.19.21
- **A co-commit can no longer re-commit bytes the quorum already rejected.** A co-commit commits on block inclusion and never runs the voter, so the content-hash dedup that keeps a rejected memory's exact bytes out was skipped on that one write path: a jointly-signed envelope could re-admit content that had been deprecated, under a fresh memory id, while the same bytes submitted through `POST /v1/memory/submit` were refused as a duplicate. `POST /v1/cocommit/submit` now consults the same lookup before it broadcasts and refuses a tombstoned hash with `409 Tombstoned content`; the envelope's own `SharedID` is excluded so an idempotent re-send still works. It is a submission-boundary check rather than a consensus rule — the consensus path deliberately reads no off-chain state — so a node that broadcasts a co-commit transaction directly, bypassing its own REST surface, is not covered by it.
- **The MCP client stopped keeping its own duplicate rule.** `sage_remember`, `sage_observe` and `sage_reflect` used to drop a write when more than 60% of its significant words appeared inside one of the first 50 committed memories in the domain — silently, order-dependently, and only on MCP, so the same write over REST or the SDK landed. They now report the node's own verdict: `POST /v1/memory/pre-validate` runs the same dedup, quality and consistency checks the vote applies, an exact duplicate comes back as `status: "skipped"` carrying the node's reason, and a memory that merely shares vocabulary with an existing one is stored instead of discarded.
- Also in this release: the `validated` status is documented as declared-but-unwritten (nothing has ever produced it, and recall would hide such a row), an unused `ValidateMemoryRecord` that duplicated the REST validator is gone, and the reference docs state plainly that knowledge triples and `access_logs` are write-only.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.19.21`. SDK 11.19.21.
- ## What's New in v11.19.20
- **Dedup rejection is sticky.** Content that was rejected, challenged, or forgotten can no longer be re-admitted by submitting the identical bytes again: the voter's dedup lookup now matches any *other* memory that has left `proposed`, not just committed ones, while a candidate can never match its own row (the v10.1 self-match fix stays fixed). Two identical submissions racing each other no longer veto each other, and a correction still passes whenever its content actually changed.
- The dedup lookup — evaluated once per pending memory on the voter's two-second poll — is now indexed on both stores. SQLite gains a `content_hash` index; Postgres drops its legacy committed-only partial index at startup and rebuilds once, which can make the first boot after upgrade slower on a large `memories` table.
- Also in this release: the README, the `sage-memory` skill, and the reference docs qualify the BFT/consensus claims for single-validator personal installs, and the papers section now cites the true published provenance.
- No consensus change or chain migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.19.20`. SDK 11.19.20.
- ## What's New in v11.19.19
- **Security dependency update:** upgrades gRPC-Go from v1.83.1 to v1.83.2, addressing [CVE-2026-84445 / GHSA-2v4p-qf9q-27wj](https://github.com/grpc/grpc-go/security/advisories/GHSA-2v4p-qf9q-27wj). The upstream fix rejects HTTP/2 requests missing both `:authority` and `Host` headers, preventing a panic in xDS servers. SAGE's CometBFT servers use ordinary gRPC servers, but the dependency is patched for defense in depth.
- No consensus or storage migration; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.19.19`. SDK 11.19.19.
- ## What's New in v11.19.18
- Federation agents now visibly orbit their nodes. Motion continues over empty map space and resumes after pointer selection; hovering an agent, keyboard inspection, and dragging keep targets steady. Pause motion and reduced-motion preferences remain supported.
- Container: `ghcr.io/l33tdawg/sage:11.19.18`. SDK 11.19.18.
- ## What's New in v11.19.17
- **See your federation.** CEREBRUM opens connected nodes as an interactive
- connectome with agent clusters, search, zoom, a List view, and a selection panel
- for exact addresses and connection controls. Gentle ambient agent drift includes
- a pause toggle, stops during interaction, and respects reduced-motion settings.
- Actual node names make the viewed
- node clear, including when you open another SAGE through a tunnel.
- A dedicated operator-only SSE stream shows recent message and reply transport
- status without exposing message text or proofs. Live changes animate when their
- endpoints are loaded; reconnecting refreshes history without replaying old
- traffic. The view is bounded, with explicit agent and node paging.
- Federation onboarding now explains **Exchange codes → Verify together → Explore
- agents**. Both confirmation screens preserve the explicit number check and
- explain that memory sharing is optional. Read, Copy, and Clear domain permissions accept
- bulk selection or drag-and-drop into a draft, with an explicit save. Removing
- trust keeps its separate confirmation and pairing-again explanation.
- No consensus-rule or application-version change; app-v27 remains the ceiling.
- Existing permissions and trust agreements stay in place.
- Container: `ghcr.io/l33tdawg/sage:11.19.17`. SDK 11.19.17.
- ## What's New in v11.19.16
- **Connect nodes, find agents, send messages.** Trusted peers running v11.19.16
- make eligible ordinary agents discoverable and messageable automatically, without
- exporting each agent or granting access to memory domains. Root identities stay
- excluded, and explicit messaging blocks still apply.
- CEREBRUM adds a searchable directory grouped by node, exact-address copying, and
- paged agent lists. Bulk selection and drag-and-drop prepare Read/Copy sharing
- choices; saving those choices explicitly grants memory access. Pairing alone
- shares no memory domains, and existing approved grants remain in place.
- MCP `sage_directory` searches local and federated agents by default. Upgrade both
- peers for automatic node messaging; older peers retain their export-based behavior.
- New sends refresh legacy recipient tickets, while queued messages retain their
- original authorization mode.
- Federated replies now accept the signed claimant-session field emitted by MCP,
- fixing peer rejection of otherwise valid replies. Reply retries report the actual
- retained delivery state and diagnostic instead of always claiming "queued".
- Existing failed events remain failed; the upgrade does not silently resend them.
- No consensus-rule or application-version change; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.19.16`. SDK 11.19.16.
- ## What's New in v11.19.15
- **Consensus-safe memory cleanup, without the 500-record cap.** CEREBRUM now
- scans the full inventory, previews verified eligible counts, and processes
- manual or automatic cleanup through existing consensus challenge transactions.
- Open tasks and internal records are protected. The UI distinguishes queued work,
- confirmed submissions, and observed outcomes instead of reporting premature success.
- Automatic cleanup requires **fresh current-Root authorization after upgrading**;
- old enabled toggles do not silently activate it. Preview does not enable cleanup.
- Exact signed transactions are saved before submission for safe recovery. A
- challenge may need further votes; audit history is retained. See the
- [cleanup guide](docs/reference/concepts/memory-cleanup.md).
- No consensus-rule or application-version change; app-v27 remains the ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.19.15`. SDK 11.19.15.
- ## What's New in v11.19.14
- **Security dependency update:** gRPC-Go is upgraded to v1.83.1 to address
- HTTP/2 DATA-frame fragmentation heap exhaustion (CVE-2026-84304, Dependabot
- alert #45). The required genproto and OpenTelemetry dependencies are refreshed
- alongside it. CodeQL workflow actions are pinned to the verified v4.37.9 commit.
- This patch introduces no consensus-rule, AppHash-input, key-encoding, fork-target,
- or application-version changes. App-v27 remains the supported ceiling.
- Container: `ghcr.io/l33tdawg/sage:11.19.14`. SDK 11.19.14.
- ## What's New in v11.19.13
- **The stdio MCP bridge no longer self-installs project hooks into the user’s
- home directory.** When `sage-gui mcp` starts with `$HOME` as its working
- directory, automatic project repair now returns without writing `.claude`
- hooks or project-relative hook registrations into user-global configuration.
- Explicit `sage-gui mcp install` and `sage-gui codex install` commands keep their
- existing home-directory refusal. Normal project-directory self-healing also
- remains unchanged, including when `CLAUDE_CONFIG_DIR` points elsewhere.
- This patch changes no consensus rule, AppHash input, key encoding, fork target,
- or application version. Existing app-v27 chains replay byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.13`. SDK 11.19.13.
- </details>
- ## Release History
- The latest release notes are above. Earlier entries below describe behavior at
- their release dates; use the current reference for present-day contracts.
- <details>
- <summary>Earlier releases — preserved changelog</summary>
- ## What's New in v11.19.12
- **Project-scoped MCP and Codex installs can no longer corrupt user-global host
- configuration.** `sage-gui mcp install` and `sage-gui codex install` now refuse
- to run when the working directory resolves to the user's home directory. Run
- the command from the intended project instead; ordinary project installs are
- unchanged.
- The native-shell build also refreshes its fail-closed checksum for the official
- September `linuxdeploy-plugin-appimage` rebuild. The replacement was produced
- by the upstream project's successful scheduled workflow from its unchanged
- source commit, and its downloaded SHA-256 matches GitHub's release-asset
- digest. An unexpected future replacement will continue to stop the build.
- This patch changes no consensus rule, AppHash input, key encoding, fork target,
- or application version. Existing app-v27 chains replay byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.12`. SDK 11.19.12.
- ## What's New in v11.19.11
- **CEREBRUM now supports operator-configured hostnames behind a local TLS
- reverse proxy.** Set `SAGE_ALLOWED_CEREBRUM_HOSTS` to an exact comma-separated
- hostname allowlist when Caddy, Traefik, or another loopback proxy preserves the
- browser-facing `Host` instead of rewriting it to `localhost`. Ports are
- normalized and wildcards are deliberately unsupported.
- The trust boundary stays local: the connected peer and every forwarded IP hop
- must still be loopback, unconfigured hostnames still fail closed, and browser
- origin matching accepts `X-Forwarded-Proto` only when every field-line and
- comma-joined token is a valid, case-insensitive `http` or `https` value and all
- hops agree. Empty, malformed, or mixed scheme chains are rejected.
- This patch changes no consensus rule, AppHash input, key encoding, fork target,
- or application version. Existing app-v27 chains replay byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.11`. SDK 11.19.11.
- ## What's New in v11.19.10
- **Returning agents can be reviewed normally again.** When app-v26 retirement
- has handed an agent's former home domain to the stable Root principal,
- CEREBRUM reapproval now binds the existing owner and uses the established
- Root-to-agent recovery transfer for that exact recorded home. Fresh or
- operator-entered domains never receive an implicit transfer.
- Rejecting a pending registration now counts active memories—the same lifecycle
- view shown by the recovery panel—instead of treating deprecated audit history
- as work the operator can still remediate. Active records continue to block
- ordinary rejection unless they are deprecated, transferred, or the explicit
- attribution-preserving force path is chosen.
- This patch changes no consensus rule, AppHash input, key encoding, fork target,
- or application version. Existing app-v27 chains replay byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.10`. SDK 11.19.10.
- ## What's New in v11.19.9
- **Codex workspace identity resolution now fails closed at the filesystem
- root.** A user-level Codex MCP process launched from `/` can no longer reuse the
- retired `global-codex` signer or auto-register the synthetic name `codex//`.
- SAGE rejects that broad, untrustworthy boundary before Git discovery,
- project-config lookup, key loading, or key generation. Real project and linked
- worktree roots continue to resolve to their stable workspace identities;
- operators who intentionally need a non-workspace shared identity must pin it
- explicitly with `SAGE_IDENTITY_PATH`.
- This patch changes no transaction, AppHash input, key encoding, fork target, or
- application version. Existing app-v27 chains replay byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.9`. SDK 11.19.9.
- ## What's New in v11.19.8
- **Access Groups now discover transferred historical domains, not only each
- member's enrollment-time home domain.** CEREBRUM's bounded caller-domain
- projection consults the consensus-maintained current-owner index for the caller
- and active local group peers. A transferred `user-*` domain therefore appears
- as a usable exact recall or write target even when its current owner never
- authored a memory there.
- Every discovered candidate is still re-authorized against current ownership,
- group authority, profile restrictions, and hard denies before it is returned.
- Per-record classification checks remain on the memory disclosure path. The
- result remains bounded and explicitly reports truncation; it does
- not expose a global domain roster, change ownership, copy grants, or weaken
- shared-domain and foreign-write restrictions.
- This patch changes no transaction, AppHash input, key encoding, fork target, or
- application version. Existing app-v27 chains replay byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.8`. SDK 11.19.8.
- ## What's New in v11.19.5
- **Claim recovery and host wake coordination now survive real multi-transport
- runtimes.** Both exact-local compatibility claim paths—`GET /v1/pipe/inbox`
- and explicit `PUT /v1/pipe/{pipe_id}/claim`—atomically bind the session and
- create its receipt, so ownership cannot commit without recovery evidence. MCP
- claimant identities are durable and transport-scoped across stdio,
- Streamable HTTP, and SSE; `claimant_identity_mode` discloses whether the
- identity is durable, a safe concurrent ephemeral fallback, inherited, or
- unavailable.
- Claim transfer remains deliberate. `sage_message_handoff` requires the exact
- `claimant_session_id` and `claim_revision` returned by passive history; stale
- or A→B→A delayed transfers fail the revisioned compare-and-swap fence. The
- direct REST route preserves pre-v11.19.5 clients by treating an omitted
- `from_revision` as 0 only, so it can move an untouched first-generation claim
- but safely conflicts after any transfer. SAGE never steals a claim merely
- because it is old.
- The new signed, payload-free `GET /v1/inbox/activity-state` returns exactly
- `{version,epoch,seq}` so host hooks can notice fresh task assignments and
- replies. The opaque 32-character database-incarnation `epoch` survives process
- restarts and backup restore, but changes for a fresh database so an old host
- cursor cannot suppress new cues after reinitialization.
- Those events remain nonblocking coordination: they do not change the exact
- three-field `{version,seq,pending}` contract of `/v1/messages/wake` or
- `/v1/messages/wake-state`, and they never make Stop treat a reply as unfinished
- work. Hooks can surface activity on the next prompt, but cannot resurrect an
- already-idle host task.
- This patch changes no consensus rule, AppHash input, transaction type, key
- encoding, fork target, or application version. The supported consensus ceiling
- remains app-v27.
- Container: `ghcr.io/l33tdawg/sage:11.19.5`. SDK 11.19.5.
- ## What's New in v11.19.4
- **Updater governance compatibility and recovery state are now one atomic
- proof.** The replacement binary reports its own maximum supported application
- version. SAGE validates canonical pending-plan and active-ballot state against
- that exact ceiling while holding the same runtime read fence that pins the
- snapshot height and AppHash. Consensus cannot publish newer governance state
- between the compatibility decision and the verified recovery snapshot.
- v11.19.3 acquired those two read fences separately. Its snapshot was coherent,
- but a concurrent Commit could make the preceding compatibility verdict stale.
- Personal single-node installs still upgrade normally in the app: v11.19.3 and
- v11.19.4 have the same app-v27 ceiling, the personal-node watchdog cannot create
- an unsupported app-v28 transition, and the updater performs the recovery
- snapshot, coordinated stop, final stopped-state snapshot, install, rollback,
- and restart automatically. No CLI or manual preflight is required. The
- stopped-node procedure in [`docs/UPGRADING.md`](docs/UPGRADING.md) is only for
- quorum or externally managed nodes where an operator can mutate governance
- during the v11.19.3 check-to-fence window.
- This patch changes no consensus rule, AppHash input, transaction type, key
- encoding, fork target, or application version. Existing app-v27 chains replay
- byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.4`. SDK 11.19.4.
- ## What's New in v11.19.3
- **Normal upgrades now preserve compatible governance state automatically.**
- The desktop updater reads the canonical pending plan and active proposal under
- one runtime-consistent view before changing the executable. A supported
- in-flight upgrade is included in the existing verified recovery snapshot and
- continues after restart; it is not a reason to interrupt the user or block the
- update. No terminal command, preflight ceremony, or governance expertise is
- required.
- Malformed canonical state, an undecodable upgrade ballot, or a target newer
- than this binary supports still fails closed before executable mutation. The
- technical `upgrade status` and stopped-node `upgrade preflight` commands remain
- available for headless and quorum operators. **Superseded safety notice:** the
- v11.19.3 live updater did not hold one uninterrupted fence across that check and
- snapshot capture. That does not impose a CLI step on a personal node; only
- quorum or externally managed governance needs the coordinated stopped-node
- procedure when leaving v11.19.3.
- This patch changes no consensus rule, AppHash input, transaction type, key
- encoding, fork target, or application version. Existing app-v27 chains replay
- byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.3`. SDK 11.19.3.
- ## What's New in v11.19.2
- **Binary replacement now has consensus-authoritative upgrade-governance
- proof.** The read-only `/upgrade/governance-status` ABCI query reports the
- current application version, the exact pending `upgrade:plan` record, and the
- canonical `state:gov:active` proposal. Upgrade ballots include their decoded
- target application version. Storage, pointer/proposal identity, bounds,
- canonical-name, status, height, and payload-decode failures return ABCI code 1
- instead of being misreported as an empty plan or ballot.
- `sage-gui upgrade status` now consumes that fail-closed query rather than
- inferring safety from `/abci_info` plus the off-chain dashboard projection. The
- stopped-node `sage-gui upgrade preflight` command uses the same canonical
- inspector before the new server starts. v11.19.3 integrates that compatibility
- decision into the normal updater and lets supported in-flight operations
- continue automatically.
- This patch changes no consensus rule, AppHash input, transaction type, key
- encoding, fork target, or application version. Existing app-v27 chains replay
- byte-identically.
- Container: `ghcr.io/l33tdawg/sage:11.19.2`. SDK 11.19.2.
- ## What's New in v11.19.1
- **Stranded message claims remain recoverable beyond the retained-history
- window.** `sage_inbox` now embeds the first passive, payload-free page of
- unfinished claims held by another runtime sharing the same exact agent identity.
- Agents can continue through every older page with
- `sage_message_history(folder="claimed_elsewhere")`, then deliberately transfer
- an exact claim through the existing compare-and-swap `sage_message_handoff`
- path after deciding that its former claimant is dead or stale.
- The recovery projection exposes only the message ID, claimant-session fence,
- timestamps, and local/federated classification needed for safe handoff. It does
- not expose sender identity, intent, payload, result, provider, or chain IDs.
- Expired TTL-bounded claims are also excluded consistently from both the exact
- diagnostic count and its recovery pages before the periodic expiry sweep runs.
- Provider-addressed compatibility messages now bind atomically to the exact
- claiming agent and MCP session, resurface on later polls, support CAS handoff,
- and complete idempotently through `sage_message_reply`. A failed reply explicitly
- does not authorize creating a substitute `sage_message_send`; agents must recover
- the original claim or report the failure. Existing claimed provider rows receive
- an off-chain SQLite `legacy` session fence during startup migration.
- This patch introduces no consensus change or application-version increase. The
- supported consensus ceiling remains app-v27.
- Container: `ghcr.io/l33tdawg/sage:11.19.1`. SDK 11.19.1.
- ## What's New in v11.19.0
- **Record authors regain lifecycle authority in reserved shared namespaces.**
- After app-v27 activates, the immutable author of a record in `general`, `self`,
- `meta`, or `sage-*` may challenge that record and may reinstate its open
- challenge without separately holding a level-3 Modify grant. The exception is
- record-scoped and does not apply to governance-promoted shared domains. Pending
- or inactive enrollment, read-only/profile restrictions, shared-write denies,
- and classification/clearance failures still deny the action. App-v21 weighted
- challenge rounds include the eligible record author in their frozen electorate.
- **Omitted task status now has one canonical meaning.** After app-v27, a signed
- new-task request that omits `task_status` is canonicalized to `planned` by both
- REST transaction construction and consensus proof verification. Pre-app-v27
- chains retain the historical requirement to send `task_status: "planned"`
- explicitly, preserving replay and AppHash compatibility.
- App-v27 is a governed consensus upgrade from app-v26 with no state migration.
- Its rules begin at H+1 after activation; older blocks replay under their original
- application version.
- Container: `ghcr.io/l33tdawg/sage:11.19.0`. SDK 11.19.0.
- ## What's New in v11.18.28
- **Reserved shared domains are readable again without becoming ownable.** Active
- local principals can read the compile-time shared namespaces `general`, `self`,
- `meta`, and `sage-*`, while each record's classification still applies. This
- restores the shared-domain behavior expected by existing agents without opening
- private or restricted records.
- Access-grant transactions now reject attempts to register either those reserved
- namespaces or governance-promoted shared domains as owned domains. REST reports
- that conflict as a forbidden request, and the API, SDK, and RBAC references now
- state the same contract.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.28 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.28`. SDK 11.18.28.
- ## What's New in v11.18.27
- **Empty semantic recall now distinguishes genuine absence from an incomplete
- vector-space view.** For an empty, domain-scoped semantic query, `index_status`
- reports `complete`, `incomplete`, or fail-closed `unavailable` only when the
- caller and exact query universe support that conclusion. The same signal is
- relayed through `sage_recall` and `sage_turn`, so write-on-absence agents can
- avoid manufacturing duplicates when committed memories are temporarily
- unreachable in the active embedding space.
- The proof is caller-safe and race-fenced across canonical projection, SQL,
- embedding-space, and vault generations. Narrowed or federated queries and
- unhealthy projections never receive a false completeness claim, while bounded
- indexed probes keep the empty-result path operationally safe.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.27 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.27`. SDK 11.18.27.
- ## What's New in v11.18.26
- **The supported Go dependency baseline is refreshed.** This release carries
- the validated `testify` 1.12.0, `x/crypto` 0.55.0, and `x/tools` 0.49.0 module
- updates already exercised by the full repository gate.
- **Code scanning and native-shell CI actions are refreshed to their pinned
- current revisions.** CodeQL runs with the updated action bundle and the native
- shell cache action is updated, without changing SAGE runtime behavior.
- **HTTP MCP tokens now bind to existing approved managed identities.** On
- app-v23 nodes, token creation no longer generates an unapprovable pending
- principal: Root/Admin selects an active ordinary agent already managed by the
- node, and issuance fails closed if its exact key is unavailable. The CLI also
- handles `mcp-token create --help` without minting a credential and rejects
- unknown creation flags.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.26 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.26`. SDK 11.18.26.
- ## What's New in v11.18.24
- **Federated inbox work now has recoverable, session-fenced ownership.** SAGE
- binds an inbound federated claim to the receiving MCP session before exposing
- its payload. Retained older claims receive an explicit `legacy` CAS fence for
- deliberate handoff; live work is never stolen by a timeout. Reply completion,
- the claimant check, encrypted result fingerprint, and durable return event now
- commit atomically, so a lost-response retry returns the original event while a
- different second reply conflicts.
- **MCP boot guidance no longer rides inside ordinary tool results.** Lifecycle
- standing stays in `initialize.instructions`, including for a client that
- initializes after its first tool call. The former imperative block that asked an
- agent to invoke tools and edit a memory file has been removed, keeping the inbox
- trust boundary internally consistent.
- **Embedding-space and retention diagnostics are more precise.** The readiness
- guard labels only a qualified-versus-bare spelling of the same provider/model
- leaf/dimension as a likely alias, without collapsing two organizations that
- publish the same basename. Durable-until-handled presentation is limited to
- actionable pending/claimed work, while mixed-version retention-only responses
- remain compatible.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.24 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.24`. SDK 11.18.24.
- ## What's New in v11.18.23
- **Turn-time recall now carries the same trust and lifecycle evidence as explicit
- recall.** `sage_turn` includes each recalled memory's `corroboration_count` and
- `status`, so the every-turn path no longer hides corroboration weight or whether
- a recalled row is committed or currently challenged.
- **Embedding-space drift is visible before it silently empties semantic recall.**
- At boot, SAGE compares the active embedder with the non-deprecated vector spaces
- already in the local store. A mismatch produces a loud warning and a structured
- `embedding_space` block in `/ready`; the node remains available by default while
- strict readiness returns 503, allowing an intentional re-embed migration to
- finish instead of turning a quality warning into an outage.
- **Managed reranker setup now diagnoses incompatible prebuilt engines.** After a
- verified install, SAGE preflights `llama-server`. Proven GLIBC, GLIBCXX, or CXXABI
- loader failures preserve the loader's real error and point operators to the
- bring-your-own reranker path instead of reporting a successful unusable install.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.23 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.23`. SDK 11.18.23.
- ## What's New in v11.18.22
- **A missing optional ForceGraph API can no longer strand CEREBRUM after the
- verified brain has rendered.** The renderer now publishes the core graph and
- truthful counts before optional anatomical, control, and interaction setup. The
- bundled runtime's absent `clickAfterDrag` helper is feature-gated, so the brain
- hull, controls, and auto-rotation continue instead of falling into the cold
- unavailable path with real nodes already on screen.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.22 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.22`. SDK 11.18.22.
- ## What's New in v11.18.21
- **A domain-summary refresh can no longer cover a verified MRI graph.** The MRI
- renderer is now the sole authority for the central unavailable overlay. Domain
- inventory failures stay localized to their own retrying panel, while genuine
- cold graph failures and unsafe mode switches remain fail-closed.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.21 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.21`. SDK 11.18.21.
- ## What's New in v11.18.20
- **A transient MRI refresh no longer hides a graph CEREBRUM has already
- verified.** Memory and Connectome snapshots now retain their explicit source
- mode. If a live refresh fails, CEREBRUM keeps the last verified snapshot visible
- only when it belongs to that same mode, while retrying in the background. Cold
- failures and failed mode switches still fail closed, so Connectome bytes can
- never masquerade as a verified memory projection.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.20 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.20`. SDK 11.18.20.
- ## What's New in v11.18.19
- **Codex project hooks stay inside their project.** The v11.18.18 byte-exact
- self-healer could mistake Codex's user-global `~/.codex` configuration directory
- for a project and generate a global `hooks.json`. That made an unrelated Codex
- task receive SAGE inbox Stop nudges for the shared agent identity. The healer now
- refuses the user-home/global scope; project-local hooks continue to self-repair.
- **Connectome clicks now have one hit-tested owner.** The redundant DOM click
- fallback that raced ForceGraph's deferred node click is gone. Small pointer
- wobble is handled by one explicit tolerance, background dismissal uses the
- graph's raycast result, and clicking a second neuron no longer closes the
- inspector and starts a competing zoom-out first. Raw domain-access metadata is
- summarized behind a bounded disclosure below traffic, relationships, and memory
- details; bloomed memory nodes now expose hover and accessible click feedback.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.19 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.19`. SDK 11.18.19.
- ## What's New in v11.18.18
- **Codex upgrades now repair stale SAGE lifecycle hooks automatically.** On
- every MCP startup, the project self-healer compares all five installer-owned
- Codex hook scripts with their fully rendered current templates. A mixed
- generation can no longer pass merely because the files exist or another hook
- mentions the current binary. Upgrading therefore replaces legacy no-op Stop
- hooks and malformed prompt hooks without requiring a second manual
- `sage-gui codex install` run.
- **The CEREBRUM Connectome now leads with the graph itself.** Neurons have a
- larger practical click target; clicking one opens its persistent identity,
- visible incoming/outgoing traffic, strongest peer, directed connection list,
- and visible memory lobe. The compact fallback selector now shows only agents
- with visible peer relationships, ordered by retained traffic, instead of
- turning a large dormant/test roster into the primary navigation surface.
- Isolated authorized neurons remain visible and clickable in the brain and join
- the selector while selected.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.18 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.18`. SDK 11.18.18.
- ## What's New in v11.18.17
- **Routine MCP restarts no longer make the same stdio agent disown its own
- unfinished messages.** The primary stdio runtime now persists one opaque
- claimant identity per exact signed agent, provider, and project under
- `SAGE_HOME`, and holds an OS advisory lock as the liveness fence. A later
- runtime reuses that identity only after the earlier process is no longer live;
- a genuinely concurrent runtime receives an independent identity and retains
- the existing one-handler and compare-and-swap handoff boundary. In-place
- installed-binary handoff also carries the current claimant identity while the
- old process keeps the lock alive.
- The fix is deliberately prospective and does not bulk-transfer historical
- claims created by pre-v11.18.17 random process identities. Those rows remain
- visible through `claimed_elsewhere_count` and passive history and can still be
- transferred one at a time with the existing CAS-fenced handoff after the old
- claimant is known dead. HTTP MCP conversations remain transport-scoped. This
- patch introduces no new consensus application version or state migration. The
- ceiling remains app-v26; **v11.18.17 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.17`. SDK 11.18.17.
- ## What's New in v11.18.16
- **Claimed agent work no longer disappears from the inbox that claimed it.**
- `sage_inbox` now returns a separate bounded `own_claimed_unfinished` projection
- for messages already owned by the exact current agent session. The projection
- is passive: it never claims, refreshes, transfers, or duplicates work, and it
- does not change the established `items` or `count` meaning of newly available
- work. Exact agent/session filtering, completion and expiry handling, bounded
- results with an exact total, reply-after-repoll, and nonmutation are pinned by
- store, REST, and MCP regression coverage.
- The payload-free hook status path also checks the durable wake snapshot, so
- claimed-but-unfinished work cannot be reported as a clean inbox merely because
- no unclaimed row remains. Older or temporarily incapable nodes degrade to an
- explicit `unavailable` state instead of either a false zero or a failed primary
- inbox call. This patch does not automatically transfer claims from another
- session; passive history plus explicit compare-and-swap handoff remain the
- recovery boundary. It introduces no new consensus application version or state
- migration. The ceiling remains app-v26; **v11.18.16 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.16`. SDK 11.18.16.
- ## What's New in v11.18.15
- **Every unfinished exact-recipient local canonical message now has a durable
- wake generation, including upgrade-era claimed-only work and sends through the
- deprecated pipe route.** Startup backfill covers both pending and claimed rows, so a recipient
- whose only live work was already claimed cannot reopen as the silent
- `{seq:0,pending:true}` state. Keyed exact-local pipe sends use the canonical
- idempotent admission path; unkeyed sends insert the row and advance the same
- recipient sequence atomically. Publication happens only after commit, exact
- replays do not republish, and an incapable backend fails before insertion rather
- than creating durable work that wake consumers cannot observe as new.
- The experimental Claude notification adapter is explicitly opt-in again. The
- shipped Claude Code host registers the custom notification handler, but
- end-to-end delivery from a plain `.mcp.json` server through its plugin-scoped
- gate remains unverified. An idle adapter would also acquire the one exact-agent
- wake lease and exclude a useful long-running consumer.
- `SAGE_CLAUDE_CHANNEL=true` enables it for an operator who has confirmed that
- delivery path.
- Pending-memory presentation is deterministic even when creation timestamps tie:
- SQLite and PostgreSQL both use `memory_id` as the final ordering key. The
- documentation citation guard now parses newline-separated and hyphenated paths,
- pins every concrete declaration/lead/interior anchor, repairs only explicitly
- accepted declaration anchors, refuses semantic locations it cannot reconstruct,
- and inventories the remaining legacy skipped and bare references. This patch
- introduces no new consensus application version or state migration. The ceiling
- remains app-v26; **v11.18.15 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.15`. SDK 11.18.15.
- ## What's New in v11.18.14
- **Durable agent messages now stay visible until the work is actually
- finished.** Claiming a message no longer makes the payload-free wake surface go
- quiet: both pending and claimed rows remain unfinished, a reconnect at the
- current cursor receives an immediate wake, and `sage_inbox` reports an exact
- payload-free claimed-elsewhere state instead of a bounded-scan false zero.
- Claude Code project sessions arm the signed wake channel by default, while the
- optional Stop hook reads a lease-free monotonic snapshot so new or stranded
- work can nudge a session once without stealing the live SSE consumer lease.
- The same recovery path is honest at its edges. A claimant-session fence
- rejection remains a typed conflict instead of masquerading as a missing
- message, and history plus explicit compare-and-swap handoff remain the only
- way to recover another session's claim. Canonical retention migration now
- rescues only the exact historical 24-hour stamp, preserving a sender's chosen
- bounded TTL across every store reopen, including RFC3339 nanosecond timestamps.
- **CEREBRUM's Connectome now identifies the agents it renders.** Hover details
- are positioned and escaped reliably, while click, tap, and keyboard selection
- open one persistent inspector with exact agent identity, visible retained
- traffic, peers, activity, and an independently loading visible-memory lobe.
- Selection survives authorized live refreshes, error and empty states stay
- truthful, mobile uses a bounded sheet, and reduced-motion and established
- Connectome guidance remain intact.
- Agent-as-lobe corroborator reads now use one deterministically ordered bounded
- batch instead of an N+1 query pattern, with matching SQLite and PostgreSQL
- ordering. The MCP contract also states the server-enforced 31-day
- `sage_timeline` range rather than advertising requests the server rejects.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.14 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.14`. SDK 11.18.14.
- ## What's New in v11.18.13
- **Hubanov's distributed-engram contribution now connects memories to the
- neurons that corroborated them.** CEREBRUM keeps agent and memory identities in
- separate graph namespaces, rejects stale bloom generations, and removes every
- transient bridge on focus or graph replacement. The server uses a deterministic,
- indexed 96-row evidence prefix and exposes at most 12 authorized bridges without
- turning historical corroboration into a claim of current possession.
- **Claude's production wake source can now arm the payload-free message bus.**
- When explicitly enabled with `SAGE_CLAUDE_CHANNEL`, the MCP runtime consumes the
- existing signed SSE wake route with a random process lease and resumable cursor.
- Delivery applies backpressure instead of dropping the newest wake, and shutdown
- releases saturated readers without leaking goroutines or claiming message
- content.
- **The Connectome no longer floats an instructional card over the brain.** Its
- guidance lives in the existing reading panel, the mode toggle keeps one stable
- name and visible pressed state in both themes, keyboard focus remains clear,
- mobile Reset behavior stays intentional, and view changes are announced to
- assistive technology.
- This patch also closes a claimant-session compatibility bypass: a current typed
- 404 is authoritative, the deprecated pipe-result alias carries the active MCP
- session, and only a genuine old-node route miss may fall back. It introduces no
- new consensus application version or state migration. The ceiling remains
- app-v26; **v11.18.13 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.13`. SDK 11.18.13.
- ## What's New in v11.18.12
- **CEREBRUM can now open an agent as a memory lobe.** Selecting a connectome
- neuron lazily blooms that agent's highest-confidence visible memories as
- engrams, while retaining the operator-only route and app-v23 per-record
- projection checks. The indexed, bounded query avoids whole-brain scans; stale,
- failed, and disposed frontend requests cannot leave another agent's lobe on
- screen.
- **Dashboard live activity is now guarded as one exact 20-event registry.** The
- seven previously unwired operator events now reach the existing dashboard SSE
- stream, while message wake, MCP, and wizard protocols stay route-local. A
- fail-closed typed control-flow audit and executable browser contract reject
- dead, aliased, escaped, build-tagged, or decoy event sinks.
- **Signed task creation and message attribution now agree end to end.** Every
- official task constructor explicitly signs the required initial `planned`
- status, and REST fails fast instead of mutating an omitted signed field into a
- transaction that app-v23 through app-v26 must reject. Authorized message and
- pipe responses retain exact immutable agent IDs alongside mutable presentation
- labels, use one bounded batch metadata query on healthy production stores with
- a bounded exact-ID fallback, suppress foreign-chain label collisions, and keep
- count-only responses identity-free.
- This patch also repairs release-facing documentation drift, pins the current
- 33-tool MCP inventory, and adds fail-closed symbol/citation coverage for the
- references it can verify. It introduces no new consensus application version
- or state migration. The ceiling remains app-v26; **v11.18.12 introduces no
- app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.12`. SDK 11.18.12.
- ## What's New in v11.18.11
- **The CEREBRUM connectome now fires live without widening its operator-only
- boundary.** Successful local message sends emit a contentless invalidation tick;
- the browser then refetches the existing caller-filtered snapshot and pulses only
- newly observed synapses. Monotonic generations preserve later ticks across
- in-flight requests, ordinary reloads, failures, and retries, while initial loads
- and unrelated refreshes never create false activity.
- **Dashboard retrieval activity no longer duplicates authorized memory plaintext
- into the global operator stream.** Recall, search, and hybrid events now expose
- only their event type and result count. The obsolete expandable plaintext panel
- is gone, and serialized-frame regressions pin the contentless contract and live,
- non-replayed delivery.
- **Claude bookend sessions can discover waiting SAGE messages without claiming or
- revealing them.** A signed, payload-free inbox-status hook reports only the
- current identity and unread count, makes failures visible, preserves unrelated
- user hooks during self-heal, and exposes the read-only message tools needed to
- perform the explicit inbox fetch.
- This patch also keys local connectome locality by chain identity, removes a stale
- app-v7 validator warning after app-v14, dims the connectome skull for legibility,
- requires patched Go 1.25.13 throughout current builders and CI, and publishes
- checksum sidecars for Windows executables. It introduces no new consensus
- application version or state migration. The ceiling remains app-v26;
- **v11.18.11 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.11`. SDK 11.18.11.
- ## What's New in v11.18.10
- **Multiple MCP runtimes sharing one agent identity can no longer silently lose
- track of claimed messages.** Every MCP conversation now has an opaque claimant
- session ID. Atomic inbox claims persist that session in passive history, an
- explicit compare-and-swap handoff transfers work between runtimes, and a stale
- former owner is rejected if it tries to reply after ownership moved. Receive
- tokens remain replay-safe after a lost response, while legacy direct REST
- clients retain their existing agent-level compatibility path.
- **CEREBRUM can render the agent message bus as a live connectome inside the 3D
- brain.** Registered agents become domain-coloured neurons, directed channels
- become traffic-weighted synapses, and hub agents settle toward the core. The
- view consumes the existing RBAC-filtered synapse projection, drops ghost edges,
- and fences asynchronous mode switches so a slow memory response can never be
- displayed as connectome data.
- **Upgrade-watchdog submissions can no longer hold a signing key's nonce lease
- for the process lifetime when CometBFT wedges.** One bounded context now covers
- both lease acquisition and the broadcast. A deadline after submission remains
- a typed indeterminate outcome, so the exact signer and bytes stay fenced until
- their fate is reconciled; elapsed time never releases the key fail-open.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.10 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.10`. SDK 11.18.10.
- ## What's New in v11.18.9
- **Ambiguous CometBFT commit and sync outcomes are now typed at the shared
- broadcaster boundary.** Transport, status, RPC, decode, shape, hash-binding, and
- missing-height failures return `ErrSubmitIndeterminate` for valid signing keys,
- while the existing live-registration path remains an independent fence
- backstop. Pre-send request-construction failures remain definitive and do not
- fence a key over bytes that never reached a transport.
- **Federation sync now fails closed if its commit broadcaster ever violates its
- contract by returning neither a result nor an error.** The exact signer and
- encoded transaction remain fenced until reconciliation proves their fate,
- instead of releasing the key for a potentially in-flight transaction. A new
- cross-package decoder contract also pins the HTTP prologue shared by
- `internal/tx` and the CEREBRUM web path while recording their deliberate verdict
- and envelope-tolerance differences.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.9 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.9`. SDK 11.18.9.
- ## What's New in v11.18.8
- **CometBFT transaction submissions no longer permit Go's HTTP transport to
- transparently redeliver a fenced request after a reused connection fails while
- reading the response.** Commit, sync, byte-identical nonce-fence reconciliation,
- and CEREBRUM submission paths now share a non-reusing HTTP/1.1 transport seam.
- Each submission call writes its transaction on one connection and returns an
- indeterminate result instead of silently delivering the same signed bytes to a
- second responder. Restart failure reporting also preserves the signer-fence
- veto ahead of a generic drain timeout.
- **MCP reply polling now fails safe when a caller presents an unsafe forward
- watermark.** If `reply_since` is later than the authoritative retained-reply
- head, or no head exists to validate it, `sage_inbox` returns the newest passive
- reply page for deduplication instead of filtering a formal reply into a false
- empty result. Complete recovered pages become a new safe baseline; truncated
- pages require composite-cursor catch-up, and failed page reads never claim
- recovery. A successful outbound `sage_message_send` also performs one bounded,
- sender-exact passive inbox snapshot so an inbound message that arrived after an
- earlier empty poll is surfaced during continued coordination.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.8 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.8`. SDK 11.18.8.
- ## What's New in v11.18.7
- **Large signed transactions now use a bounded CometBFT transport instead of
- overflowing request headers.** Existing smaller broadcasts keep the established
- GET wire shape, while large commit, sync, and byte-identical nonce-fence
- reconciliation requests use JSON-RPC POST with base64 transaction bytes. Client
- transaction and JSON-RPC body limits are independently range-checked, capped at
- 8,000,000 bytes, and refuse an oversized request before send. Operators raising
- them must configure matching CometBFT limits. Independently, every validator
- enforces a 1,200,000-byte aggregate raw-transaction budget for app-v20 atomic
- finalization, sufficient for the measured 1,304-entry SkillRegistry transaction.
- Memory content remains bounded at 512 KiB, while the canonical signed
- `AgentRequest` proof has its own 600,000-byte consensus bound, admitting the
- measured 573,723-byte proof without widening the content or aggregate limits.
- Response handling accepts strict quoted or numeric `int64` heights, rejects
- fractional, exponent, null, malformed, and out-of-range heights, and refuses
- unsupported content types.
- **Federation route refresh no longer risks recursively acquiring the
- sync-policy read lease from a peer-request caller.** Opportunistic refresh
- admission is policy-free and bounded to one pending refresh per peer; the
- agreement and binding lookup runs asynchronously after the request caller can
- release its lease. Failed-request and successful-Direct triggers remain
- covered, while the route-exchange endpoint does not self-trigger refresh.
- **P2P-only peers can recover when their stored route snapshot is missing or
- belongs to an older trust generation.** Only the authenticated
- `/fed/v1/p2p/routes` bootstrap exchange may use stale or current route addresses
- as connection hints; the current agreement's pinned mTLS identity remains
- authoritative. Protected requests reject missing or cross-generation snapshots
- with `trust_generation_mismatch`. A matching-generation empty target set remains
- explicitly pinned and cannot fall back to current configuration.
- **Federation diagnostics now give security evidence precedence over route
- availability evidence.** Mixed route-availability plus certificate, SPKI, pin,
- identity-mismatch, or security-block evidence is classified as
- `security_blocked`; revocation, expired or unknown agreement, trust-failure, or
- authentication evidence is classified as `trust_failure`. Both verdict classes
- outrank route availability.
- This patch introduces no new consensus application version or state migration.
- The ceiling remains app-v26; **v11.18.7 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.7`. SDK 11.18.7.
- ## What's New in v11.18.6
- **Updater snapshots now prove both supported CometBFT layouts before they are
- published or reused.** Application Badger and persisted consensus state must
- match at height `H` and agree on the application hash. A blockstore committed
- through `H` is accepted only after its `H` block ID and seen commit match that
- state. If the blockstore is durably one block ahead at `H+1`, SAGE additionally
- verifies the complete block and part identity, direct-parent and state-derived
- header fields, last and seen commits, validator signatures, and CometBFT's
- replay-time block validation. Regression coverage restores the candidate and
- runs the real CometBFT handshaker, proving exactly one replayed block and safe
- restart reuse. Malformed or more-than-one-ahead provenance is rejected, and an
- invalid prior publication is quarantined before a valid replacement can be
- published. Cancellation always blocks executable updater handoff, although a
- safe snapshot may already have been atomically published. Non-empty `H+1`
- evidence is retryable until application and state catch up.
- **Federation Retry now performs one bounded, exact-generation recovery
- workflow.** Concurrent operator clicks share the same route refresh and
- authenticated status probe. Direct and relay targets are frozen to the active
- JOIN generation, HTTP `401`/`403` and certificate/identity failures stop before
- re-probing, and a revoke or re-pair during the response invalidates the result.
- Typed dashboard diagnostics distinguish missing or expired route bundles,
- stale Direct routes, unavailable relays, trust-generation changes, and legacy
- connections that must be paired again. Ordinary polling and mutating requests
- do not enter this retry path.
- **Memory-reassignment audit failures no longer place request-controlled agent
- IDs in logs.** The source and target are represented by fixed 96-bit truncated
- SHA-256 fingerprints (24 lowercase hexadecimal characters), preserving stable
- incident correlation without allowing CR/LF or other control characters to
- forge log records.
- This patch does not change consensus state or application activation. The
- ceiling remains app-v26; **v11.18.6 introduces no app-v27**. The signer fence
- also remains process-local: unresolved submissions still require proof of fate,
- and crash/restart or a separate signing process is not claimed safe until
- durable cross-process pre-broadcast intent exists.
- Container: `ghcr.io/l33tdawg/sage:11.18.6`. SDK 11.18.6.
- ## What's New in v11.18.5
- **Long-lived stdio MCP sessions now follow an installed SAGE upgrade without
- executing a request under stale tools.** The MCP process snapshots the exact
- executable that started it. If the app bundle or binary is atomically replaced,
- the next unread JSON-RPC frame is handed to the new executable together with
- the remaining stdio stream. The upgraded runtime—not the stale process—receives
- that request. The old runtime never executes the handed-off frame; transport
- failure remains an ordinary indeterminate outcome for callers to reconcile.
- Sessions initialized on 11.18.5 advertise MCP tool-list change support; the
- replacement emits `notifications/tools/list_changed` only after the logical
- session has completed initialization, so conforming clients refresh cached
- definitions as well as runtime behavior.
- **The unified coordination response identifies its live contract.** Every
- `sage_inbox` result now carries `coordination_schema: "sage.inbox.v2"`, the
- running `mcp_runtime_version`, and `sender_replies_embedded: true|false`. Monitors can
- therefore reject or report a stale pointer-only session instead of silently
- assuming that an empty addressed inbox also means no threaded reply arrived.
- The existing bounded `reply_items`, inclusive watermark, composite catch-up
- cursor, and passive sender-only authorization remain unchanged.
- The upgrade from a pre-11.18.5 MCP process still requires one agent-session
- restart because that already-running older process cannot contain this handoff
- logic. Once a session starts on 11.18.5 or later, subsequent binary replacements
- use the automatic request-preserving handoff. Clients that ignore the negotiated
- tool-list notification must still re-list tools or reconnect to discover new
- definitions.
- The consensus ceiling remains app-v26; **v11.18.5 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.5`. SDK 11.18.5.
- ## What's New in v11.18.4
- **One inbox poll now surfaces both new work and threaded answers.**
- `sage_inbox` returns replies to messages you sent under the separate passive
- `reply_items` key by default, while genuine inbound work remains under `items`.
- Reply rows never inflate work counts and explicitly require no reply. Inclusive
- `reply_since` polling prevents same-millisecond loss; truncated pages fail safe
- with an exact composite-cursor catch-up action and forbid advancing the
- watermark until the window is drained.
- **Release builders now enforce the patched Go floor.** Root and `natter`
- modules require Go 1.25.12, CI and release jobs resolve that exact `go.mod`
- toolchain, every Go container builder uses 1.25.12, and pinned
- `govulncheck v1.6.0` scans both modules before either CI fan-in or release
- publication can pass.
- **Legacy pipeline retention compares time chronologically and conservatively.**
- SQLite purge eligibility no longer relies on variable-width RFC3339 text.
- Cutoffs are floored to SQLite's millisecond precision, so ambiguous
- same-millisecond rows are retained rather than deleted early; malformed read
- evidence also retains fail safe.
- The consensus ceiling remains app-v26; **v11.18.4 introduces no app-v27**.
- Container: `ghcr.io/l33tdawg/sage:11.18.4`. SDK 11.18.4.
- ## What's New in v11.18.3
Lines 2,001–2,701 are not shown. The link to the file on GitHub has every line.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.