ContextLattice v3.17.3 - Trust Before Magic

Before memory gets more magical, its floor gets harder. This release turns six quiet assumptions into contracts the runtime can prove.

Private on disk

Sensitive local stores now use owner-only access: restrictive POSIX modes on Unix-like systems and protected user, system, and administrator ACLs on Windows. Existing stores migrate through a bounded, resumable process instead of one unbounded startup rewrite. Symlink targets must remain inside the intended store, and runtime responses expose opaque store references instead of host paths.

No approval, no work

The task worker checks approval before runner selection, context expansion, inference, adapter execution, or memory writeback. A blocked task is now cheap, inert, and explicit.

Advice earns confidence

Runner quality recommendations require at least five samples per runner. Sparse candidates remain visible for operators, but they cannot outrank evidence-qualified candidates by accident. The best eligible candidate is retained even when the response is bounded.

History stays honest

Temporal claim queries exclude retracted assertions by default. Retractions remain durable and explicitly queryable, preserving audit history without contaminating current-state recall.

One task contract

Agent guidance now names the canonical /agents/tasks route family. A repository audit rejects stale task-route vocabulary before it can spread across harness instructions.

Native means registered

Strict runtime ownership no longer relies on a hand-waved inventory. Required native routes are deduplicated, recall routes are represented, and tests resolve every required path through the gateway mux.

Boundaries preserved

• The CLI remains the primary interaction path.
• Public and paid lanes retain their existing feature boundaries.
• No third-party harness is installed automatically.
• No new daemon, scheduler, or Python live-runtime dependency was added.
• Public artifacts expose no private planning material or machine-local paths.

Verification

The release gate covers repeated and race-enabled Go tests, Pi/Droid task-worker tests, output-contract and profile audits, public lane and leak guards, owner-only migration and symlink cases, approval-before-work regression tests, temporal-status behavior, runner sample eligibility, exact native-route registration, live runtime health, and rollback rehearsal.