lattice-recall
lattice-recall is the durable local outbox and opportunistic Nexus sync layer for the Lattice family. It provides a synchronous SQLite write path (WAL mode) for zero-loss local capture, paired with an asynchronous background coroutine that syncs records to the Nexus POST /api/recall endpoint when connectivity allows. All records are UUID-keyed for idempotent delivery, retried with exponential backoff on transient failures, and vacuumed after a configurable retention window (default 30 days).
Quickstart
pip install lattice-recall
import lattice_recall
await lattice_recall.persist(record)
Local-Only Mode
By default, lattice-recall requires Nexus connectivity. For early consumers or offline-first workflows, disable Nexus sync:
store = RecallStore(nexus_enabled=False)
await store.persist(record)
Local-only mode uses SQLite for all durability. Full details on the Nexus dependency and migration path: docs/NEXUS_DEPENDENCY.md.
Spec
The complete design specification for v0.1.0 lives in the Lattice vault:
02_Projects/Lattice/lattice-recall/Specifications/2026-04-27 lattice-recall v1 - Design Spec.md
Acceptance Gates
All gates covered by tests. See vault spec for full detail on each gate.
| Gate | Test Path |
|---|---|
| G1 sync local write durability | tests/test_store_persist.py |
| G2 async Nexus sync | tests/test_sync_worker.py |
| G3 reachability gating | tests/test_nexus_client.py |
| G4 burst on reconnect | tests/test_net_up_event.py + smoke B2 |
| G5 idempotency | tests/test_idempotency.py + tests/test_nexus_client.py |
| G6 cross-device ordering | tests/test_store_fetch_local.py |
| G7 retention | tests/test_retention.py |
| G8 multi-source | tests/test_store_fetch_local.py + smoke B4 |
| G9 multi-tenant slot | covered via Record.tenant_id |
| G10 failure visibility | tests/test_telemetry.py |
| G11 manual drain | tests/test_store_lifecycle.py |
| G12 local-only retrieval | tests/test_store_fetch_local.py |
| A1-A10 unit tests | tests/test_*.py per gate |
| B1-B5 smoke gates | tests/smoke/test_smoke_b1_to_b5.py |
| C1-C3 perf gates | tests/perf/test_perf_c1_c3.py |
License
Proprietary. All rights reserved.
Version: 0.1.0 (2026-04-27)
Metadata
Release files for lattice-recall 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lattice_recall-0.1.0.tar.gz | 24.9 kB | Without provenance | Details for lattice_recall-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lattice_recall-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for lattice_recall-0.1.0-py3-none-any.whl |
Total release size: 39.7 kB
Release files / lattice_recall-0.1.0.tar.gz
| Download URL | lattice_recall-0.1.0.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73fd4286c766107117d90e46885ac84ba87a7325087316762409952ebb0d53dd
|
|
BLAKE2b-256 checksum How to use checksums |
3af07aa9ded8c457f0e10f289bd3be3b6d0208d7b2866d2b94b001d7b4e9c856
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Release files / lattice_recall-0.1.0-py3-none-any.whl
| Download URL | lattice_recall-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d62af7808e80e13405965101cdc1e7562410f732247bf4cad462b456357d60a
|
|
BLAKE2b-256 checksum How to use checksums |
5b75421e233f5c96c8251729f6b23baf0e2542d066b5e61433d08053d90b9835
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Security for lattice-recall 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.