Workspace
/workspace is not ephemeral scratch space. It is the durable working state for a q15 stack.
What lives here
Section titled “What lives here”- Your project files and working directory
- Embedding source registry at
/workspace/.q15/embed/sources.json - Embedding sync state at
/workspace/.q15/embed/state.jsonl - Any files the agent creates, edits, or downloads during its work
Persistence model
Section titled “Persistence model”| Deployment | Expectation |
|---|---|
| Kubernetes | Required PVC (q15-workspace) |
| Docker Compose | Required named volume or bind mount |
| Local development | May start empty, populated later |
A newly created stack may attach an empty persistent volume. That empty initial state is valid. Operators may populate it later through normal agent work or manual setup.
The key expectation is that /workspace remains attached to the same stack over time. Restarts, redeployments, and upgrades should preserve the existing volume. Do not downgrade it to an ephemeral mount (emptyDir, anonymous volume, or temporary bind location).
What does not live here
Section titled “What does not live here”- Agent identity and memory live under
/memory - Skill artifacts live under
/skills - Nix store state lives under
/nix - Proxy state lives under
/var/lib/q15/proxy
These are separate persistent volumes, each with its own ownership and lifecycle.