# Personal and shared workspaces

> Personal and shared spaces — the sharing boundary for memory.

A **workspace** is the sharing boundary — who can see this memory. It's a
different question from what a memory is *about* (that's a
[project](/docs/organizing)), and the two are kept apart on purpose.

## Personal and shared

- Your **personal** workspace is a private space of one, and the default.
  Anything captured without a destination lands here.
- A **shared** workspace is a team you and others co-own. You can be a member of
  many.

Your agent's reads **span every workspace** you belong to, so it answers from
all your memory at once. Its writes **default to personal**; a memory only
enters a shared space when it's sent there deliberately.

## Routing — where a memory belongs

Each shared space carries a **charter** — a short statement of what belongs
there — and you can keep private per-space notes about what you share and what
you hold back. Your agent reads both before filing a memory, then routes it:

- a clear match to a shared space's charter → it goes there;
- clearly personal → it stays personal;
- unsure → it **parks in personal, asks you, and moves it** on your answer.

Memory is never quietly shared. When in doubt, it stays yours until you say
otherwise.

## The shared Dreamer

A shared space is tended like any other — by one member at a time. The Dreamer
takes a short [lease](/docs/dreamer) on the space before working it, so two
members never dream it at once. Each member's nightly run works the shared
spaces they belong to, in turn.

Creating a shared space and managing its people are human actions — see
[Members and roles](/docs/members).