Repository navigation
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:
multipleuses set membership;
singleuses 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/setand 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 multivaluecoexistreconciliation 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.0Existing 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.