Product updates and rollout notes

Channel command bridge live, with optional Qdrant Cloud gRPC validation

• Added orchestrator-native messaging endpoints for OpenClaw/ZeroClaw, Telegram, and Slack command routing.
• Added command parsing for @ContextLattice remember|recall|status with project/topic directives.
• Added a one-shot 04:30 MT launch gate scheduler command and status/cancel controls.
• Added Qdrant Cloud BYO connectivity check script that validates both HTTP and gRPC paths while keeping local-first default behavior.

Public beta hardening and release packaging complete

• Added launch-readiness gate automation for authenticated load, queue drain, backup/restore drill, and production security preflight simulation.
• Published release image lockfile for reproducible deployments with pinned digest references.
• Finalized legal package (terms, privacy, DPA baseline, acceptable use, subprocessors, commercial licensing baseline).
• Published public messaging package and next-track messaging-surface expansion plan.

New integrations guide, dark visual refresh, and faster sink fanout tuning

• Added a dedicated Integrations page for ChatGPT app, Claude chat apps (desktop and web), Claude Code, Codex, and OpenClaw/ZeroClaw wiring.
• Moved public overview pages to a dark-first theme and aligned navigation across Home, Architecture, Updates, Installation, and Troubleshooting.
• Expanded compose env passthrough for fanout and Mongo pool tuning to speed queue drain and improve sustained write throughput.
• Documented the default launch path (gmake mem-up) and explicit full/lite commands for local-first deployment.

Landing page now explains each service and why it exists

• Added component-by-component breakdown for Orchestrator, Memory Bank, Qdrant, Mongo, MindsDB, Letta, outbox, and retention.
• Added explicit “benefit + why” summaries so operators understand service intent at a glance.
• Connected these components directly to learning retrieval outcomes and ranking quality over time.

New pilot landing page published

We shipped a new public pilot page with a clearer value narrative and current platform capabilities.

• Headline focus: fix context drift before it burns token budget.
• Pilot structure: week-by-week baseline, optimization, and ROI readout.
• Capability highlights: coalesced fanout, backlog-aware Letta admission, and sink retention.
• Trust framing: private-by-default, BYOK-compatible, local-first operation.

Orchestrator learning schema + Letta RAG emphasis

The orchestrator becomes more accurate over time by learning from feedback signals and applying preference-aware reranking during retrieval. This learned ranking is further supported by RAG via Letta archival memory, alongside Qdrant semantic recall and raw-source fallbacks.

• Learning loop reinforces what sources and patterns are actually useful in your workflows.
• Federated retrieval merges Qdrant, Mongo raw, MindsDB, Letta, and memory-bank lexical fallback.
• Result quality improves iteratively as the learning schema accumulates real operator feedback.

Queue and storage safety upgrades

• Fanout coalescer reduces duplicate hot-file writes before they hit outbox depth.
• Letta admission control protects throughput by shedding low-value Letta writes under backlog.
• Low-value retention sweeps for Qdrant and Letta keep storage pressure bounded.
• Shared HTTP client pools and batched fanout improve write-path efficiency.