Skip to content

ContextLattice v4.0.0: Aggregate Signal

Choose a tag to compare

View all tags
@sheawinkler sheawinkler released this 19 Jul 20:11
v4.0.0
0b94224
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.0

Memory That Compounds Without Giving Itself Away

ContextLattice v4 closes the Frontier 30 program with Aggregate Signal: a bounded path for learning from system outcomes without exporting the memories, prompts, projects, paths, or identities that produced them.

The CLI remains the primary interface. Preview is local and non-persistent. Queueing requires explicit opt-in. Cohorts smaller than 20 disappear behind suppression. Privacy composition is bounded. Replays cannot become differencing probes. Opt-out deletes unreleased work and never pretends an already released aggregate can be recalled.

What Shipped

  • contextlattice_aggregate_signal and contextlattice aggregate-signal for preview, queue, report, status, opt-out, and entitled governance.
  • Five versioned contracts for contribution, report, accounting, paid governance, and secure-aggregation research boundaries.
  • A strict allowlist of clipped numerical and categorical sufficient statistics.
  • Recursive rejection of raw text, memory, prompts, embeddings, paths, project names, exact timestamps, secrets, and stable installation identifiers.
  • One contribution per installation commitment, metric, and week.
  • Cohort suppression below 20, per-release epsilon at most 0.25, rolling 90-day epsilon at most 2.0, and delta at most 0.000001.
  • Owner-only atomic ledgers capped at 64 MiB and 100,000 records.
  • Idempotent reports, changed-parameter differencing rejection, expiry, revocation, and hash-linked paid audit receipts.
  • Aggregate-ready quality, policy, and Context Mesh source statistics without changing retrieval or memory-write behavior.
  • Closed-world public, paid, and development projections that mechanically reject paid or research implementation leakage into the wrong artifact.

Commercial Boundary

The public runtime ships the local Aggregate Signal core. Operator and Enterprise artifacts add credential-derived workspace isolation and governance. Production paid contribute and report remain hard-blocked until six independent privacy and utility reviews pass.

This is a controlled preview, not a formal privacy certification. The release ships enforceable minimization, suppression, accounting, replay, retention, and consent controls while refusing to market pending evidence as finished proof.

Why v4

The Frontier train changed the category of the product. ContextLattice no longer only remembers. It proves continuity, measures context utility, explains retrieval, learns policy under gates, adapts briefs to agents, moves work without dissolving trust, evolves verified skills, removes cold starts, and can now learn aggregate system signal without surrendering raw memory.

See docs/aggregate-signal.md for the operating contract.

Assets 2
Loading