ContextLattice v3.17.2 - Your Models. Your Disk.

ContextLattice should remember your work, not annex your startup disk. This release gives local model storage an explicit address and proves that the running container honored it.

Local-first, on storage you chose

Set OLLAMA_DATA to an absolute path and the existing Ollama service mounts that location at /root/.ollama. Leave it unset and ContextLattice preserves the backward-compatible home-directory default.

There is no new storage daemon, migration service, or required package. The override uses the existing Compose path and works anywhere that path is valid for the local container runtime.

Configuration becomes evidence

Startup storage verification now includes Ollama. It compares the expected source with the running container's actual mount and fails if they diverge. Configuration no longer gets credit for intent alone.

The shipped environment examples also quote values containing spaces. They remain readable documentation, but they are now valid Bash input too. A regression test sources every shipped profile so future copy changes cannot silently break operator workflows.

Boundaries preserved

• Quickstart behavior is unchanged when OLLAMA_DATA is unset.
• ContextLattice does not move or delete existing model data automatically.
• The public core receives the generic override and verifier.
• Paid delivery retains its existing entitlement and artifact boundaries.

Verification

The release gate covers default and overridden Compose renders, live mount verification, shell-sourceable environment profiles, public and paid lane guards, repeated Go gateway tests, and a live relaunch with model readback from externally mounted storage.