Skip to the field note
Subsystem · spaces + memory5 minute read

Context should have an address

A space is where the work, its instructions, its history, and its disclosure boundary meet.

01Filesystem
02Space contract
03Canonical memory
04Derived index
05Scoped prompt

The filesystem already knows where the work is

Most software work already has a durable address: a repository, a worktree, a directory, a thread attached to a project. Voxelbox uses that existing shape instead of inventing a parallel universe inside a chat product. A space is the bounded context where artifacts belong and where agent membership, disclosure policy, and event routing are scoped.

That means the repository contract can live with the repository. The instructions an agent needs, the project files it may change, and the git history that protects those changes remain inspectable with ordinary tools. The context survives whether Voxelbox is running or not.

Files are canonical; indexes are expendable

Human-readable Markdown holds durable memory and decisions. SQLite and full-text indexes make retrieval faster, but they are derived views. I should be able to delete the index, rebuild it from the files, and recover the same source truth.

This is not an argument against databases. Foundry uses structured state where transactional behavior earns it. It is an argument against putting the only copy of hard-won context behind an opaque retrieval layer that will eventually be replaced.

Retrieval is a projection, not memory itself

A session does not need every fact a space has ever retained. It needs the smallest useful projection for the current task: relevant instructions, recent decisions, known failure patterns, and the files actually in play. The retrieval layer assembles that projection. The space remains larger than the prompt.

This distinction is what makes model-agnostic inference credible. The model receives context from Voxelbox; it does not become the permanent home of that context.

Location is also policy

A space answers more than “where is the file?” It answers who may see it, which tools are available there, where events should appear, and what can travel if the work is packaged or federated. Private by default becomes enforceable when disclosure is attached to a bounded context.

The directory is the address. The space contract says what the address means.

A prompt is temporary. The place the work belongs should not be.