zara-memory: symbolic scoped memory integration

lost-rob0t commented

2026-08-31 18:42:42 +00:00

(Migrated from github.com)

Plugin

zara-memory

Goal

Provide Zara with scoped symbolic memory that can store structured facts plus lossless text when needed, while keeping memory separate from transient context.

Memory scopes

Support at minimum:

session
user
project
machine
global

Operations

remember
recall
forget
assert_fact
retract_fact
explain_memory
list/search by scope, type and provenance

Integrate with lost-rob0t/symbolic-memory where appropriate rather than building an incompatible parallel memory model.

Semantics

facts have stable IDs/provenance/timestamps;
natural-language payloads can be retained losslessly;
symbolic projection is the default retrieval surface where possible;
forgetting a memory must remove/repair related projections instead of leaving orphan facts;
plugin consumers can define memory schemas without gaining unrestricted access to every scope.

Integration

zara-context supplies short-lived context but does not auto-persist it;
zara-coding can read/write project-scoped workflow facts;
zara-contacts, zara-home and other domains can contribute typed facts;
zara-expert can query relevant memory projections through explicit boundaries.

Acceptance criteria

all initial scopes are represented and isolated
structured facts and full-text memories are both supported
recall returns provenance and stable IDs
forgetting cleans associated symbolic projections
plugin-specific schemas can be registered safely
transient context is not persisted implicitly
deterministic tests cover scope isolation, update and forgetting
README documents storage backend/configuration and privacy semantics
registry validation, plugin tests and nix flake check pass

## Plugin `zara-memory` ## Goal Provide Zara with scoped symbolic memory that can store structured facts plus lossless text when needed, while keeping memory separate from transient context. ## Memory scopes Support at minimum: - session - user - project - machine - global ## Operations - `remember` - `recall` - `forget` - `assert_fact` - `retract_fact` - `explain_memory` - list/search by scope, type and provenance Integrate with `lost-rob0t/symbolic-memory` where appropriate rather than building an incompatible parallel memory model. ## Semantics - facts have stable IDs/provenance/timestamps; - natural-language payloads can be retained losslessly; - symbolic projection is the default retrieval surface where possible; - forgetting a memory must remove/repair related projections instead of leaving orphan facts; - plugin consumers can define memory schemas without gaining unrestricted access to every scope. ## Integration - `zara-context` supplies short-lived context but does not auto-persist it; - `zara-coding` can read/write project-scoped workflow facts; - `zara-contacts`, `zara-home` and other domains can contribute typed facts; - `zara-expert` can query relevant memory projections through explicit boundaries. ## Acceptance criteria - [ ] all initial scopes are represented and isolated - [ ] structured facts and full-text memories are both supported - [ ] recall returns provenance and stable IDs - [ ] forgetting cleans associated symbolic projections - [ ] plugin-specific schemas can be registered safely - [ ] transient context is not persisted implicitly - [ ] deterministic tests cover scope isolation, update and forgetting - [ ] README documents storage backend/configuration and privacy semantics - [ ] registry validation, plugin tests and `nix flake check` pass

nsaspy referenced this issue

2026-09-08 02:02:59 +00:00

zara-memory: reject duplicate projection cleanup identities #106

nsaspy referenced this issue

2026-09-08 02:02:59 +00:00

zara-memory: reject duplicate recall identities #109

nsaspy referenced this issue

2026-09-08 02:03:00 +00:00

zara-memory: bound projection cleanup evidence from forget #112

nsaspy referenced this issue

2026-09-08 02:03:00 +00:00

zara-memory: enforce fact cardinality on backend recall evidence #113

nsaspy referenced this issue

2026-09-08 02:03:00 +00:00

zara-memory: bound backend recall result cardinality #115

nsaspy referenced this issue

2026-09-08 02:03:01 +00:00

zara-memory: reject boolean JSON-RPC response identities #120

nsaspy referenced this issue

2026-09-08 02:03:01 +00:00

zara-memory: require explicit boolean MCP tool result status #121

nsaspy referenced this issue

2026-09-08 02:03:01 +00:00

zara-memory: normalize native symbolic-memory OS launch failures #122

nsaspy referenced this issue

2026-09-08 02:03:01 +00:00

zara-memory: reject non-MemorySchema registrations at service boundary #123

nsaspy referenced this issue

2026-09-08 02:03:01 +00:00

zara-memory: validate schema descriptor types at registration boundary #124

nsaspy referenced this issue

2026-09-08 02:03:01 +00:00

zara-memory: bound symbolic fact collections before normalization #125

nsaspy referenced this issue

2026-09-08 02:03:02 +00:00

zara-memory: reject malformed memory-type selectors with structured errors #127

nsaspy referenced this issue

2026-09-08 02:03:02 +00:00

zara-memory: isolate expected provenance from backend mutation during write verification #130

nsaspy referenced this issue

2026-09-08 02:03:02 +00:00

zara-memory: reject backend mutation of remembered source evidence #131

nsaspy referenced this issue

2026-09-08 02:03:02 +00:00

zara-memory: reject incomplete symbolic fact terms #132

nsaspy referenced this issue

2026-09-08 02:03:02 +00:00

zara-memory: reject malformed scope values structurally #133

nsaspy referenced this issue

2026-09-08 02:03:03 +00:00

zara-memory: reject backend memories with empty provenance #135

nsaspy referenced this issue

2026-09-08 02:03:03 +00:00

zara-memory: type-check recall queries before backend dispatch #136

nsaspy referenced this issue

2026-09-08 02:03:03 +00:00

zara-memory: reject backend-injected facts outside registered schema #141

nsaspy referenced this issue

2026-09-08 02:03:04 +00:00

zara-memory: enforce backend memory-type isolation #147

nsaspy commented

2026-09-08 02:03:50 +00:00

Owner

Auto-RAGE dependency check after merging #85: the Zara-side scoped adapter, registry/Nix packaging, lifecycle/degraded status, scope/schema enforcement, and deterministic fake-backend tests are green. I am leaving #7 open because the canonical lost-rob0t/symbolic-memory main README still explicitly says full-corpus memory_search, symbolic-first memory_recall, and natural-language forgetting are not implemented. zara-memory will not invent a parallel persistence/retrieval model or falsely expose those operations as available. Next dependency-ready slice is to bind those capabilities once the canonical backend publishes them; until then unsupported recall/forget paths continue to fail explicitly.

Auto-RAGE dependency check after merging #85: the Zara-side scoped adapter, registry/Nix packaging, lifecycle/degraded status, scope/schema enforcement, and deterministic fake-backend tests are green. I am leaving #7 open because the canonical `lost-rob0t/symbolic-memory` main README still explicitly says full-corpus `memory_search`, symbolic-first `memory_recall`, and natural-language forgetting are not implemented. `zara-memory` will not invent a parallel persistence/retrieval model or falsely expose those operations as available. Next dependency-ready slice is to bind those capabilities once the canonical backend publishes them; until then unsupported recall/forget paths continue to fail explicitly.

nsaspy commented

2026-09-08 02:03:51 +00:00

Owner

Native symbolic-memory integration advanced in merged #91 (600aa339…). Zara now has approval-gated memory.remember plus authorized memory.get through the current stateless MCP contract, with host-bound authority, fixed argv/no shell, secret-minimized child env, writable-state rejection under /nix/store, and explicit native scope limits (session/project/global).

#7 remains open intentionally: current symbolic-memory still does not implement full-corpus search, symbolic-first recall, or forgetting/projection cleanup, so Zara does not emulate or claim those acceptance items.

Native symbolic-memory integration advanced in merged #91 (`600aa339…`). Zara now has approval-gated `memory.remember` plus authorized `memory.get` through the current stateless MCP contract, with host-bound authority, fixed argv/no shell, secret-minimized child env, writable-state rejection under `/nix/store`, and explicit native scope limits (`session/project/global`). #7 remains open intentionally: current symbolic-memory still does not implement full-corpus search, symbolic-first recall, or forgetting/projection cleanup, so Zara does not emulate or claim those acceptance items.

nsaspy referenced this issue

2026-09-08 02:19:10 +00:00

fix: reject duplicate memory projection identities #291

nsaspy referenced this issue

2026-09-08 02:19:11 +00:00

fix: reject duplicate memory recall identities #294

nsaspy referenced this issue

2026-09-08 02:19:20 +00:00

fix: type-check zara-memory recall query #324

nsaspy referenced this issue

2026-09-08 02:19:23 +00:00

fix: require finite zara-memory MCP deadlines #333