Skip to content

ContextLattice v3.17.5 - Current Means Current

Choose a tag to compare

View all tags
@sheawinkler sheawinkler released this 14 Jul 09:49
v3.17.5
8d24964
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ContextLattice v3.17.5 - Current Means Current

Memory should compound. State should not.

A live position, policy snapshot, runtime mode, or queue watermark has one job: tell the truth now. v3.17.5 gives that truth its own exact-state lane, keeps stale copies out of semantic memory, and closes the last paths that could let yesterday's state masquerade as today's answer.

One exact truth

  • Operator-configured runtime-state mirrors overwrite their canonical file instead of accumulating semantic history.
  • Exact state stays out of rollups, graph confidence, access learning, Qdrant, pgvector, and ordinary memory fanout.
  • A final gateway barrier suppresses stale exact-state rows from every retrieval source, including old external indexes.
  • Rust accelerators and Mongo-derived snapshots consume the same bounded path registry, while Meilisearch deletes state documents that predate the boundary.

Private without the startup punishment

  • Owner-only migration streams fixed-size directory batches instead of sorting an unbounded tree in memory.
  • Startup performs one short bounded slice, then a single cross-process-locked background worker finishes the repair.
  • Durable receipts bind completion to root identity and writer policy; legacy or mismatched receipts are reverified.
  • Unix enforcement is descriptor-relative, Windows uses protected ACLs, and health/status surfaces expose opaque store references rather than host paths.

No registry, no guess

  • The gateway creates an owner-only empty registry before readers recover.
  • Rust readers fail closed when the registry is missing, malformed, oversized, or contains unsafe path keys.
  • Reader mounts remain read-only; only the two intended storage owners can mutate the shared memory volume.

Boundaries preserved

  • The CLI remains the primary interaction path.
  • Public and paid feature boundaries remain intact.
  • No third-party agent harness is installed automatically.
  • No new daemon, scheduler, or Python live-runtime dependency was added.
  • Public artifacts contain no private planning material or machine-local paths.

Verification

The release gate covers full and race-enabled Go tests, Go vet, Linux release tests for both changed Rust crates, rustfmt, Clippy with warnings denied, Windows changed-surface compilation, full and lite Compose rendering, exact-state and owner-only audits, public lane and leak guards, source-integrity checks, installer workflows, live cutover, and rollback rehearsal.

Assets 5
Loading