This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+4 more
Summary
AI summaryEnforces non-degradable topic_rollups to fail‑open and prevents timeouts caused by aggressive staged budgets.
Full changelog
ContextLattice v3.3.2
This release bumps the public runtime with two integrity fixes on the Go retrieval path.
Included since v3.3.1
fix(gateway-go): prevent topic_rollups section timeouts with cache + timeout floor(#126)- Adds Go memory-store rollup cache (TTL + write invalidation).
- Adds
topic_rollupssync timeout floor to stop aggressive staged budgets from causing false timeouts. - Tunes scoped rollup fanout sizing for section reads.
feat(gateway-go): enforce non-degradable topic_rollups fail-open lifecycle(#127)- Marks
topic_rollupsas non-degradable by default. - Introduces protected lane policy for request-level degradation decisions.
- Ensures timeout/error on non-degradable lanes continues asynchronously instead of hard-degrading user outcome.
- Marks
Operational impact
- Section-scoped reads now remain fail-open and stable under load.
- Requests return
pending/partialwhere appropriate instead of harddegradedwhentopic_rollupsis the only delayed lane.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About sheawinkler/ContextLattice
Private-by-default memory and context layer for agents with Go/Rust runtime, staged retrieval across fused data backends, and long-horizon context continuity.
Related context
Related tools
Beta — feedback welcome: [email protected]