ContextLattice v5.0.0: Durable Work. Exact Evidence.
v5.0.0 is the stable tag for a major authority and persistence upgrade. Agent-task execution, graph state, recall evaluation, response composition, and release artifacts now participate in explicit, fail-closed contracts instead of relying on process success or implicit ownership.
The CLI remains the primary interface. HTTP, MCP, and the dashboard remain companion surfaces.
What Changed
- Gateway Go and SQLite-WAL are the sole durable authority for agent-task lifecycle state. Claims carry exact worker, instance, generation, lease, task, and attempt fences; runner exit is an observation, not publication or completion.
- Task results and artifacts are validated before durable publication. Immutable receipts bind content, result, writeback, delivery, and cleanup authorization, while restart reconciliation returns only the exact attempt-bound surface.
- Local deterministic execution uses a digest-pinned cached OCI image with no network, a read-only root, dropped capabilities, bounded resources, one task worktree mount, exact container identity, and receipt-authorized cleanup. Provider execution remains separately governed.
- Current-state and graph repair use bounded transactional persistence, authenticated commitments, exact replay and rollback evidence, cross-process fencing, and fail-closed recovery from partial writes.
- Structured graph references bind current source and target state, durable edge evidence, pagination custody, and restart recovery rather than promoting unbound or stale relations.
- Graph evaluation reaches the complete production response seam without writeback side effects. Final-visible evidence is bound to compiler rank, exact graph provenance, immutable source snapshots, and a fixed top-five scoring contract.
- Recall responses retain hard exclusions, temporal partitions, conflicts, omissions, and source membership through terminal continuation. Action evidence is non-executable unless every authority and lifecycle condition agrees.
- Release workflows rescan the exact public and paid artifact sets, validate nested packages and portable paths, bind SBOM and provenance receipts, and keep promotion dependent on independently downloaded final assets.
Compatibility
This is a major-version boundary because durable task, worker identity, graph persistence, response, and release contracts changed together. Upgrade the Gateway, global agent tools, and runner integration as one tested set. Older evidence and v4 release artifacts remain historical and are not rewritten.
Existing memory and task data are preserved in place. Startup migrations are owner-only, bounded, and restart-safe; if exact source, fence, or schema evidence is unavailable, the affected operation fails closed instead of silently importing or reassigning state.
Verification
Release verification includes focused adversarial and race tests, full Go and platform builds, generated-contract checks, Python and shell static checks, real cached OrbStack isolation tests, closed response and graph-evaluation ledgers, release-tree privacy guards, native installer inspection, and exact public/paid artifact hashes.
Hosted CI is supplemental status. The release decision remains bound to the exact locally tested source, projected lane commits, downloaded artifact set, and live rebuilt runtime proof.
Upgrade and Rollback
Preserve owner memory, task, session, Passport, continuation, graph, and policy state. Stop only the inventoried Gateway service, install the matching v5 Gateway, tools, and runner surfaces, then rebuild and restart that service. Verify /health, native route ownership, one durable task lifecycle, one isolated cleanup receipt, exact graph recovery, one compositional response, explicit silence, and installed CLI parity.
Rollback is tag-pinned. Restore the prior Gateway, tools, and runner binaries together; retain durable stores; keep canary allocations at zero; and do not down-convert v5 evidence into an older schema. Operators should resolve any v5-only pending task or migration receipt before reopening writes on the prior release.