Repository navigation
v1.3.1
Memory correctness fixes
- Deleted records stay deleted (#64). They're excluded from
get(REST and MCP),linksand recall's graph arm. Facts learned from a record are kept, but no longer point back to it. - Beliefs track their facts (#65). Editing or deleting a fact marks the entity's observation stale, and the next consolidation rebuilds it from the facts that remain. Stale observations are no longer presented as current.
- Recall is bounded (#68):
- query length, limit,
max_tokensand date ranges are validated; - the retrieval arms run in parallel, each with a deadline, so a slow embedding provider can't hold up keyword and graph results;
- entity matching uses an index instead of scanning every entity.
- query length, limit,
- Search filters are applied first (#69):
- source, type and date filters apply before results are cut to the limit, so matches aren't lost;
- paging and
has_moreare exact, and dates compare as datetimes; - body text has its own full-text index.
- Merges are atomic (#72):
- entity merges run in one transaction;
- merging two entities that both have observations leaves one observation, to be rebuilt;
- concurrent writes produce one entity and one observation per subject.
All verified by the full browser suite in CI against a real SurrealDB. Images are multi-arch (amd64 + arm64).
Updating
Settings → Updates → Update now.