Skip to content

Releases

Aletheia Memory 1.8.0

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 18 Oct 21:33
98d9265

Aletheia Memory 1.8.0 — predicate semantics and conflict governance

Release date: October 18, 2026 (America/Chicago). Python 3.11+, API v1 and
storage marker 1.3.1 remain supported. This release adds public APIs and stricter
conflict validation. Existing databases need an additive schema migration.

Highlights

  • Declare namespace-scoped predicate cardinality: multiple uses set membership;
    single uses exclusive values and remains the default for undeclared predicates.
    Declarations govern conflict detection, candidate screening, inference promotion
    and receiving-side federation reconciliation.
  • Configure declarations through Python Memory.set_predicate_semantics, HTTP
    GET/POST /v1/predicate-semantics, aletheia predicates get/set and sync/async
    SDKs. Remote writes require admin access; namespace authorization applies.
  • Close project/privacy authorization bypasses before conflict mutation, keep
    subsequent single-valued assertions disputed, and preserve approved unchanged
    contextual and temporal scopes on rescans.
  • Reject malformed, overlapping or incomplete conflict outcomes atomically;
    support explicit multivalue coexist reconciliation and consistent comparisons.
  • Complete OpenAPI URI parameter declarations and typed conflict contracts;
    validate the entire document and ship matching TypeScript starter declarations.

Upgrade guidance

See the upgrade guide. Back up before opening existing data
with automatic migration. Services using auto_migrate=False must explicitly
apply migration before startup. Roll back by restoring the matching older backup
with its older binary; an unchanged storage marker does not imply downgrade safety.
Declaring a predicate does not automatically resolve historical disputes.

Qualification and limits

The predicate implementation and seven review fixes were merged in PR #72 after
all 16 CI checks passed, including nine native OS/Python combinations, installed
wheel/source recovery and TypeScript contracts. Release-specific evidence is in
the verification record; publication receipts
and file hashes are attached to the GitHub release after publication.

The 1.7.0 production support boundaries
continue to apply. This release does not repeat or expand those measured live-model
or soak claims. Predicate declarations express application policy; they do not
infer cardinality from arbitrary language or automatically repair old disputes.

Release validation

  • Full local Python suite passed (three expected skips).
  • Baseline release gate, strict wheel/source metadata checks and embedded README comparison passed.
  • Isolated wheel and source onboarding and 1.7.0 backup-backed upgrade/recovery checks passed.
  • Release PR: #73
  • Upgrade guide.

All 16 release PR checks passed, including all nine native OS/Python jobs.
Release source: 98d9265037420c57825266f2cf9b9ce61c465f49.

Publication verification

Published to PyPI through
successful trusted publication.
All tagged native checks, distribution build and strict metadata checks passed.
PyPI's actual description and both distribution READMEs match the finalized source.
Downloaded wheel and source SHA-256 hashes match PyPI metadata. A fresh uncached
pinned PyPI install passed CLI startup and persistent predicate-semantics smoke checks.
See attached verification.json and SHA256SUMS for publication receipts.

python -m pip install --upgrade aletheia-memory==1.8.0

Existing databases need the additive migration described in the upgrade guide,
including deployments already using storage marker 1.3.1.

Separate main-push gate failure

The main-push gate
failed Windows/Python 3.11 in
test_provider_wait_does_not_block_health_or_an_unrelated_write[0.5-file]: the
health future exceeded its 750ms response deadline. The release PR and tagged
publication matrix passed unchanged, including this platform, but do not erase
that separate failure. The fixture injects a 500ms preparation delay again on
transactional remember reauthorization, after preparation was already signaled.
A test-only correction
passed five repeated local concurrency runs and all 57 retrieval-boundary tests;
native CI is pending. The original failure's complete timing
cause is unproven. No published artifact or tag has been changed.

Aletheia Memory 1.7.0

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 17 Oct 17:14
5338534

Aletheia Memory 1.7.0 — governed memory production release

Release date: October 17, 2026 (America/Chicago). Version 1.7.0 is the first
production/stable release within the support boundaries below. Python 3.11+,
API v1 and storage 1.3.1 remain unchanged. This minor version adds capabilities
and intentionally stricter validation without changing the stable API version.

Highlights

  • Fix zero-strength feedback and prevent evidence-free assistant repetition from
    increasing confidence. Reject invalid context budgets and incomplete conflict
    scope resolutions; commit complete resolutions atomically.
  • Validate all eight advisory LLM tasks. Extraction selects source-bound scope
    references, preserves negation/attribution, refuses invented calendar boundaries
    and detected qualifier loss, and records at most two independently validated
    repair attempts. Human-approved date boundaries survive promotion. Named-project
    inclusions/exclusions use actual namespace-local project context.
  • Create Windows database/archive files and internal scratch directories with
    native protected DACLs. Inspect existing directories and destination permissions
    before reserve, restore or SQLite copies write bytes; refuse broad grants.
  • Remove reverse DNS from plain HTTP and TLS listener startup. Add repeatable
    HTTP-readiness regression targets to the nine-platform CI matrix.
  • Add standard MCP JSON-RPC stdio and correct custom-namespace authorization.
    Clear console data after logout/auth loss, discard late responses, surface
    action errors and include selected namespaces in federation requests.
  • Preserve refused legacy databases, reject dangling database paths, move HTTP
    compaction outside a transaction and preserve disk-full errors through rollback.
    Add executable conformance probes and a reusable live qualification harness.

Upgrade guidance

Back up existing databases using the documented authenticated backup workflow and
verify recovery before upgrading an important deployment. API v1 and storage
version 1.3.1 remain unchanged. No model download or hosted credential is required;
configure the intended providers explicitly. Defaults are not a quality guarantee.

Windows deployments need a private database parent with trusted ancestors;
existing shared directories are refused rather than silently re-permissioned.
Choose a new private location or have the owner deliberately provision suitable
permissions. Local pairing remains POSIX-only. Extraction wire metadata advances
to candidate_claim_draft.v2 with source-bound scope_ref; integrations inspecting
raw provider schemas must account for this. Public candidates still expose the
resolved suggested scope. Budget, advisory and scope validation is intentionally
stricter; callers must handle validation errors instead of relying on coercion.
Feedback with strength zero is inert, and repeated assistant confirmations without
independent evidence no longer raise confidence.

Qualification and limits

Implementation 6256f35 passed 1,104 local tests, all fourteen milestone scorecards,
all nine native OS/Python combinations, fresh artifacts and installed recovery,
interface/TypeScript/official MCP checks and bounded disk/memory recovery. Real
Llama3.1:8b/Nomic checks passed eight advisory tasks and twelve extraction probes,
with manual review of every triple and scope. Ninety startup samples passed;
maxima were 1.297s new and 0.562s current. A 1,800-second measured soak passed
2,540 lifecycle cycles, integrity, cleanup and source stability.

Production support is within the documented boundaries, not a
claim of exhaustive correctness. Every model proposal remains untrusted pending
human review; English calendar/named-project anchoring is a bounded grammar.
Windows ACL isolation covers other standard principals with trusted ancestors,
not administrator/SYSTEM or offline disk access. Startup targets cover the stated
small-database baseline, five samples/profile, without provider loading, workers,
advertisement or pairing; they are not a population latency SLA. An initial
Windows 3.12 health-concurrency timeout passed unchanged on repeat; its cause is
unproven. The soak accumulated monotonic execution across host suspensions and
does not establish uninterrupted availability.

See qualification and step-by-step journal,
repeatable harness, and
security boundaries. See the 1.7.0 release qualification and
upgrade guide. Publication receipts and distribution hashes
are attached to the GitHub release.

Concurrency gate interpretation

The 750ms Windows 3.12 health-concurrency timeout recurred on the prepublication
main gate. No release was tagged from that failed run. Its log did not separate
request preparation from response work, so the original timing cause remains
unproven. The regression now bounds authenticated request preparation separately,
then retains the original 750ms response deadlines and requires both operations
to finish before the deliberately paused provider is released. Delayed-authentication
cases exercise this distinction. This is provider-isolation evidence, not a
750ms end-to-end health SLA; startup acceptance budgets are unchanged.

Publication verification — October 17, 2026

Published successfully to PyPI
through trusted publishing run 39052890035.
All native release-commit checks, distribution build and strict Twine validation
passed before upload. The actual workflow wheel and sdist match public PyPI
SHA256 metadata; PyPI's description exactly matches the finalized README and the
package declares Production/Stable maturity.

A fresh uncached public PyPI installation outside the checkout passed isolated
1.7.0 runtime/site-packages checks, CLI startup, dependency consistency,
Python/TypeScript onboarding and installed upgrade/restore recovery from 1.6.2.
The earlier publication gate also exercises recovery from 1.6.0. Actual
distributions, SHA256SUMS, source provenance, artifact verification and sanitized
postpublication verification receipts are attached to this release.

python -m pip install --upgrade aletheia-memory==1.7.0

Aletheia Memory 1.6.3 (beta)

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 16 Oct 14:03
4ad75a8

Documentation-only packaging correction. Runtime behavior is unchanged from 1.6.2.

  • Include the corrected publication/upgrade documentation in package artifacts and PyPI's description.
  • Replace the stale version-specific latest-release claim with stable GitHub latest-release and PyPI project links.
  • Keep the security policy's beta statement independent of a particular version.

The corrected README was checked in actual wheel metadata and the source archive before tagging. Python remains 3.11+, API remains v1, and storage remains 1.3.1.

python -m pip install --upgrade aletheia-memory==1.6.3

The semantic provider fix is unchanged: explicitly configure ALETHEIA_SEMANTIC_PROVIDER=ollama_style for HTTP semantic retrieval and preserve the index's existing embedding model/dimension/prefix settings.

Publication verification: trusted workflow 38912758161 passed, including 846 tests on each of Python 3.11, 3.12 and 3.13. Both the version-specific and project-level public PyPI descriptions exactly match the finalized tagged README. Stable latest-release links are present and the stale latest-version claim is absent. Actual workflow wheel/sdist hashes match public PyPI metadata. Exact files, checksums, source provenance and verification receipts are attached.

The simple index/project metadata initially showed the prior version during propagation; uncached retry succeeded. All documentation was finalized and built descriptions checked before tagging. These postpublication results are recorded here without changing the package or release tag.

Fresh uncached PyPI installation verified installed version, site-packages import origin, CLI and dependency compatibility. Installed Python/TypeScript onboarding passed in 23.343 seconds of automated execution (not installation time or a human walkthrough). Installed verification receipt attached.

Aletheia Memory 1.6.2 (beta)

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 16 Oct 13:28
42e7525

Aletheia Memory 1.6.2 is a beta patch release fixing HTTP semantic retrieval.

  • Select the service's semantic provider explicitly with ALETHEIA_SEMANTIC_PROVIDER=ollama_style or [server] semantic_provider = "ollama_style". The default remains mock.
  • /v1/search and /v1/retrieve use the operator's configured provider and existing matching model/dimension/input preset.
  • Lexical fallback is reported as retrieval_mode: lexical; the additive semantic_status distinguishes positive vector matches, unavailable matches, and lexical-only requests.
  • Incompatible configured HTTP-provider dimensions require explicit reindexing even without input prefixes.

Python remains 3.11+, API remains v1, and storage remains 1.3.1. No database migration or Desktop permission expansion is required.

The unchanged installed Desktop 0.1.0 b6fc845 passed live Nomic acceptance: original and corrected scores exactly matched SDK retrieval, pending corrections showed fallback, and superseded/forgotten facts stayed excluded.

Upgrade the service's own Python environment, then restart it with the desired provider setting:

python -m pip install --upgrade aletheia-memory==1.6.2

Upgrade guide · Acceptance evidence

Publication verified: the trusted PyPI workflow succeeded; wheel/sdist hashes match public PyPI metadata. A fresh uncached PyPI installation reported 1.6.2 and passed installed Python/TypeScript onboarding. Checksums, source provenance and verification receipts are attached. Corrected documentation and the publication verification record are maintained on main; release-tag artifacts remain immutable.

Aletheia Memory 1.6.1 (beta)

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 13 Oct 10:53
2f8cc18

Memory 1.6.1 beta fixes the independently verified 1.6.0 review findings and the additional procedure rollback regression. All 52 tracked issues are linked to the fix PR and its acceptance ledger.

The release closes federation recipient/identity injection paths, namespace and privacy escapes, and non-atomic lifecycle/replay operations. It corrects procedure update/rollback retrieval, Unicode search, confidence history growth, redaction residue, and conservative job recovery. Provider redirects, archive sizes and private file output are hardened.

Encrypted backup manifests now authenticate their semantic fields. Unauthenticated legacy imports require explicit trust and a destination namespace. Federation mutations use stable identifiers; administrative operations require scopes appropriate to their targets. Read the upgrade guide before updating callers or planning binary rollback.

Validation: 836 synthetic acceptance cases; Python 3.11/3.12/3.13 isolated-distribution matrix; generated TypeScript contracts and packaged starters; installed wheel/sdist onboarding and recovery against published 1.6.0; strict Twine metadata. Exact CI and artifact provenance accompany the draft assets.

Fix PR #62 · Review resolution and issue mapping · Changelog

Published on GitHub and PyPI. The trusted publishing workflow succeeded. A fresh uncached PyPI installation passed dependency, installed-version, CLI and Python/TypeScript onboarding checks. Published wheel/source hashes match the verified GitHub assets.

Install: python -m pip install aletheia-memory==1.6.1.

Aletheia Memory 1.6.0 (beta)

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 21 Sep 02:50
ac4f3b5

Memory 1.6.0 is a beta release for development and evaluation. It contains all 29 audit repairs and the nine additional defects found by independent behavioral review.

Changes

  • Enforce current scope, privacy, source and provider permissions across reads, conflict resolution, cached replies and background work.
  • Preserve federation privacy and provenance, verify peer identities, and apply deletion notices only to content actually shared.
  • Make forget modes, conflict decisions and ranking/context policies execute their intended effects; avoid stale provider results and duplicate job execution.
  • Upgrade the cryptography dependency and the development OpenAPI parser dependency, and refresh the packaged TypeScript schema.

Install and upgrade

python -m pip install --upgrade 'aletheia-memory==1.6.0'

Python 3.11+ is supported. API v1 and storage schema 1.3.1 are unchanged; upgrading from 1.5.0 requires no storage migration.

Use the beta upgrade guide for a fresh start with disposable data or a data-preserving upgrade. It covers stricter authorization, claims-only bundle privacy labels, provider approval, session-summary defaults and rejected backup combinations. Existing real-data use of affected sharing/import features may require the documented recovery procedures; a historical scanner and production qualification are outside this beta's scope.

Verification

The release PR passed all seven CI gates, including 768 tests on each of Python 3.11, 3.12 and 3.13. Local macOS validation also passed 768 tests. Fresh wheel/source installations passed Python/TypeScript onboarding, upgrade from the actual published 1.5.0 package, TLS pairing, restart/crash recovery and encrypted restore. A client paired under 1.5.0 retained its authorized access after upgrade while plaintext and out-of-namespace requests remained rejected.

See the full changelog, verification record, and release PR #8.

The publishing workflow reruns the release gates on the tagged commit before making the 1.6.0 distributions available on PyPI.

Publication verified

Both distributions are published on PyPI. Their SHA-256 hashes match the publishing workflow artifacts. Fresh wheel and source installations each passed dependency checks and all 12 Python/HTTP/TypeScript onboarding checks. The published description and packaged help match the release source.

f86580b52e353751d778474581c04c377da0459ce6157208203ea805aad24f2a  aletheia_memory-1.6.0-py3-none-any.whl
75d3c04c657c30e75e73e03ff04fad06fa56ac6bb19e8b4e13a279fa0cf5a1ec  aletheia_memory-1.6.0.tar.gz

Aletheia Memory 1.5.0

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 07 Sep 00:57
022c4f2

Memory 1.5.0 adds automatic local discovery and owner-approved pairing to the 1.4.1 baseline.

  • Running POSIX loopback services advertise expiring local registrations, renew them automatically, and remove their own registration on orderly shutdown.
  • Owners issue five-minute, single-use pairing codes with explicit namespaces, read/audit/review permissions, privacy ceilings, and credential lifetimes.
  • Pairing pins a persistent database-bound TLS certificate before exchanging secrets. Paired credentials require that encrypted identity and support expiry and revocation with secret-free audit records.
  • Service naming, directory configuration, opt-outs, protocol documentation, and recovery guidance are packaged with Memory.
  • Existing databases specified with quoted ~ paths now start without requiring --auto-migrate. The packaged TypeScript schema includes the new pairing models.

There is no database migration or locked dependency upgrade from 1.4.1. Storage remains 1.3.1.

Validation includes 330 tests across Python 3.11–3.13 in protected CI, installed wheel/source onboarding and recovery, generated consumer contracts, and packaged TypeScript starters. Recovery covers restart, SIGKILL, real registration expiry, encrypted backup restore, identity loss, and revocation. macOS arm64 checks additionally exercise cryptography 49.0.0 and 50.0.1.

Before downgrading to 1.4.1, revoke all pairing-issued credentials: that version does not enforce their TLS binding. Restored/relocated databases or lost identity files require fresh pairing. Windows local pairing, LAN/remote pairing, automatic stale-record pruning, and Desktop distribution/browsing/review remain future work.

Install or upgrade:

python -m pip install --upgrade aletheia-memory==1.5.0

Pairing and recovery guide · Release verification

Aletheia Memory 1.4.1

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 02 Sep 04:10
5e0c92b

Aletheia Memory 1.4.1 corrects the hyperlinks in the project description shown
on PyPI.

The 1.4.0 description used repository-relative README links. Those links work
on GitHub but do not resolve correctly from a PyPI release page. Version 1.4.1
uses absolute GitHub targets for the documentation, license, contribution,
security, and changelog links and adds a release gate to prevent relative README
links or images from being published again.

Runtime behavior is unchanged. The 67 runtime Python files in the 1.4.1 wheel
are byte-for-byte identical to the published 1.4.0 wheel.

Install or upgrade with:

python -m pip install --upgrade aletheia-memory==1.4.1

Full release gates passed on Python 3.11, 3.12, and 3.13, including wheel and
source-distribution onboarding, contract generation, and the packaged
TypeScript starter.

Aletheia Memory 1.4.0

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 02 Sep 03:31
6f208bd

Aletheia Memory 1.4.0 adds explicit integration contracts and a safer path from captured evidence to reviewed memory.

Highlights:

  • Typed discovery, scoped-read, governed-review, and candidate-first onboarding profiles.
  • Generated Python, browser, and TypeScript consumers with executable contract checks.
  • Zero-model embedded and HTTP agent starters with a separate operator approval step.
  • Optional local embedding and structured-extraction recipes; core remains model-free.
  • Consistent namespace, project, privacy, provenance, replay, and revision enforcement.
  • Stronger protected-storage, restore, export, key-rotation, throttling, idempotency, validation, and diagnostic behavior.
  • Storage schema 1.3.1 with atomic migration from 1.3.0 and restore-based recovery guidance.

Before upgrading an existing database, create and verify a pre-upgrade backup. Older binaries refuse storage schema 1.3.1; use the preserved old backup to return to an older release.

Memory remains independent of Desktop and Relay. Python 3.11 through 3.13 are supported. No model, Node dependency, external account, Desktop installation, Relay service, or npm package is required by the core distribution.

See CHANGELOG.md and the packaged 1.4.0 migration and integration guides for compatibility details.

PyPI: https://pypi.org/project/aletheia-memory/1.4.0/

Aletheia Memory 1.3.1

Choose a tag to compare

@khaledgabal2 khaledgabal2 released this 22 Aug 23:52

Patch release to align the GitHub release, tag, and PyPI package.\n\n- Includes the documented aletheia_client.py compatibility import module in the wheel distribution.\n- Adds the GitHub Actions Trusted Publishing workflow for TestPyPI and PyPI.\n- No runtime behavior changes.\n\nPyPI: https://pypi.org/project/aletheia-memory/1.3.1/