Skip to content

ContextLattice v3.20.3 - Receipts Before Release

Choose a tag to compare

View all tags
@sheawinkler sheawinkler released this 18 Jul 17:37
v3.20.3
8565ae2

ContextLattice v3.20.3: Receipts Before Release

ContextLattice already refused to publish a paid artifact whose source identity drifted. v3.20.3 closes the next gap: exact source proof is necessary, but it is not enough. A release must also satisfy the complete evaluation contract behind its product claim.

The CLI remains the primary interface. HTTP remains the integration fallback.

What changed

  • Release provenance now runs the complete program eval-ledger audit for Utility Ledger releases, in addition to commercial-truth validation.
  • The release ledger carries exact causal arms, denominator separation, latency, cost, tool calls, bounded storage, failure review, rollback, independent review, and negative entitlement evidence as one contract.
  • Starter and Team retain read-only Utility Analytics. Governed efficiency-policy evaluation is now correctly bound to Operator and Enterprise.
  • The policy response contract identifies frontier_verified_efficiency_operations; analytics remains frontier_utility_analytics.
  • Focused regressions prevent a commercially valid but program-incomplete ledger from reaching the installer workflow again.

What did not change

  • The public local Utility Ledger, exact token accounting, CLI receipts, and readback behavior.
  • Causal gain still requires exact matched controls; negative gains and exclusions remain visible.
  • Policy evaluation remains advisory-only. It cannot silently mutate retrieval policy or ordinary memory.
  • Third-party agent harnesses remain optional, and the CLI remains the prescribed product path.

Release lineage

Public v3.20.2 remains a valid release. The paid v3.20.2-public-paid tag stopped before any installer asset was built and remains asset-free. v3.20.3-public-paid is the first paid patch in this train authorized by both the exact-source and complete-evaluation gates.

Rollback

Disable GO_UTILITY_LEDGER_ENABLED to stop the derived ledger without changing authoritative Context Pack outcomes, exact token-impact rows, or session verification events. Efficiency-policy operations fail closed outside an entitled Operator or Enterprise runtime.

Assets 5
Loading