What Is an Ideaspace?

Imagine you are preparing for a conversation with a partner. You want last month's decisions beside today's research, with an agent who understands the work. You do not need to move everything into a new folder. You need a way to bring the right things into view.

That is a Space: a lens on the material you are working with, and a boundary for the work you do together. It holds references, not the content itself. It grants no access to what it points at.

The view is not the material

Your pages and their history live in a Repo, short for repository. A Repo remains a Repo whether one Space points to it or several do. Changing the view does not move its pages.

A Vault is the larger coordination layer: the personal or company world in which Repos, Spaces and other work are organised. A Space selects a view of that world; it is not another name for a Vault or a Repo.

For the partner conversation, the Space's Map can point to the decisions and research where they already live. The material gives your agent something to think about. Guidance stored in _agent/ in a Repo explains how to work there. A language model supplies the reasoning; the agent supplies tools for taking steps. The Space brings the relevant work into view.

Sharing a view is not sharing its contents

The shared Space we are building follows the same distinction. People are invited into a common view. Each side adds references to its own material and separately gives people access to that material. Permission to add items or invite people concerns the Space itself, not the content it points at.

A reference is not a key. Someone may see that a document is relevant without being allowed to read it. They need to request access — a knock — and its owner decides. Joining the Space must not unlock everyone's documents.

Local and remote Spaces are separate views that can change independently. They are not two automatically synchronised copies of one Space.

What works today

As of 4 November 2026, Repos are available, and local Spaces use Maps to bring material into view. The web's Space page is being built. Hosted Spaces, Space invitations and Space permissions are not available yet; the shared example above explains the design, not a workflow you can use today.

Requesting access to existing hosted Repo content already works. That does not make Space invitations available.

Underneath the local material, pages are ordinary Markdown files. People and agents can read the same pages, and those files remain useful outside any one application.