Skip to content

ContextLattice v4.0.2: One Product. One Truth.

Choose a tag to compare

View all tags
@sheawinkler sheawinkler released this 20 Jul 12:07
v4.0.2
d8ef634
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ContextLattice v4.0.2: One Product. One Truth.

ContextLattice v4 made durable continuity, explainable retrieval, portable context, verified skill evolution, and privacy-bounded Aggregate Signal part of one coherent agent intelligence layer. The product worked. Its public surfaces still described pieces of that system as if memory infrastructure were the whole story.

v4.0.2 closes that gap. The CLI remains the primary interface. The dashboard, HTTP, and MCP remain companion surfaces.

What Changed

  • One canonical machine-readable contract now owns the current version, category, interface hierarchy, official URLs, source-license split, and five public product pillars.
  • A lane-aware public-product-truth audit fails closed on version, category, license, private-boundary, local-path, release-note, static-link, fragment, CSS-asset, Mermaid, dashboard-auth, and generated-plan drift.
  • The public story now leads with the outcome: open an agent and the mission, evidence, risks, and next move are already there.
  • The website now presents the full v4 intelligence loop from durable continuity through retrieval receipts, portable context, verified skills, and Aggregate Signal.
  • The launch-flow Mermaid source uses Mermaid-safe comments, eliminating the rendered syntax error.
  • The public roadmap now describes current outcome targets and proof gates instead of presenting the completed V3 program as active.
  • The dashboard Overview uses the same five product pillars and keeps estimated token savings visibly labeled as an estimate.
  • Pricing now uses the generated commercial plan contract and the current dashboard design system, with free local use separated clearly from hosted or governed paid capabilities.
  • Public dashboard authentication remains off by default; hosted/private authentication remains explicitly enabled by AUTH_REQUIRED=true.
  • Dashboard auth mode now resolves once at runtime and is shared across the shell and pages, preventing build-time mode drift and session-provider races between account-free and hosted deployments.
  • Anonymous hosted Install visits no longer probe the paid artifact catalog; local Settings makes no private workspace requests; hosted private pages and APIs fail closed through redirect or JSON boundaries.
  • Global billing administration now requires its dedicated platform credential, reconciliation GET is permanently dry-run, SCIM token management is gated by an active Enterprise feature entitlement, and successful password logins no longer consume the failure budget.
  • Static-site publication now requires a clean, audited source tree and an exact annotated lane tag before it can update gh-pages; robots.txt, the complete sitemap, and generated commercial truth are mandatory deployment inputs.
  • Rust workspace metadata now matches each source lane and every internal crate is explicitly non-publishable.
  • The dashboard capability rail is a balanced three-by-two desktop grid with the existing single-column mobile flow, eliminating orphan-card rows without changing the visual system.

License Boundary

  • The public ContextLattice repository is Apache License 2.0.
  • Commercial and private source lanes remain Business Source License 1.1, with the configured Apache-2.0 change license.
  • Public documentation contains no non-public runbook references or machine-specific paths.

What Did Not Change

  • Gateway, retrieval, storage, session, runner, and inference runtime semantics.
  • The CLI-first agent contract or the role of dashboard, HTTP, and MCP as companion surfaces.
  • Aggregate Signal consent, clipping, cohort suppression, privacy accounting, replay, expiry, revocation, or opt-out behavior.
  • The controlled activation preview and independent privacy/utility review hold on production cohort learning.
  • The open-core boundary: useful local continuity and retrieval remain public; paid lanes add distribution, governance, protected operations, and advanced analytics.

Upgrade

Existing v4 installations can update normally. No data migration or new required service is introduced by this release.

Assets 5
Loading