Documentation

Basin is not an app you open. It is a place your AI tools reach, so the first step happens inside the tool you use most.

There are no commands to learn. The agent reads the instructions Basin gives it; you need one sentence at the start of a conversation so it knows to look.

From then on it reads what it needs before answering, and writes what it learns.

Give it something it can reuse tomorrow.

The second tool never met you, and did not have to be told.

A grant covers a whole space, not one file, and it includes anything added to the space later. Say who, and Basin does the rest.

They get an email with a link, readable in a browser immediately, and can connect their own AI to it. You see every read they make; they cannot re-share it.

Connections are per machine. A laptop and a server each need their own; revoking one leaves the other working.

An agent that begins cold reads the wrong things or nothing at all. Put its first two moves in CLAUDE.md.

# CLAUDE.md

On startup, read the Basin guide resource,
then read _overview.md in the space you are working on.

Append what you learn to worklog.md before the session ends.

A headless session is the same connection with no human in the loop.

Seventeen in total, in six families. Your client will list them; the guide resource describes each one in full.

Everything is a Markdown file with a small block of frontmatter at the top. It opens in any editor, and the export is the same files in a zip. There is no proprietary format to be trapped in.

A write records who owns it, when it happened, which version it produced, and which family of client made it. The owner is verified from the sign-in. The client family is what the tool says about itself.

Writes create versions rather than replacing history. A revoke stops future reads and does not erase past ones. Deleting a space removes its files, and leaves its events in your log marked as belonging to something that no longer exists.

You can read, download and edit your files on the web. An edit saves a new version attributed to you, exactly as an assistant's write would be — nothing is overwritten in place, and every earlier version stays readable.

If an assistant changed the file while you had it open, Basin shows you both versions rather than choosing one. Frontmatter is not editable on the web, because tags there can control who can read a file; changing those is a share, and shares happen where you can see the receipt.

You see every read of every space you own, including reads by people you granted access to. They see their own activity and nothing else: not yours, and not each other’s.

Ask the tool a question it can only answer if Basin is really there.

The Connect page shows the same thing from the other side.

Putting the one-line instruction into a Project or custom instructions works, and saves you saying it. It does not change when tools are picked up. A conversation started before the connector existed still cannot see it.

The activity log is the tiebreaker. If a read happened, it is there with a timestamp; if the page is empty, the tool never called Basin, and the problem is the connection rather than the content.