Documentation
Folders and versions
Folders — the core concept
It's folders and files, all the way down. The top level of an organization holds folders only, and every document lives in one. A folder nests folders and files inside it, just like a filesystem. History is kept per document: each document has its own line of versions, so editing one never rewrites another and nothing is ever silently overwritten. Permissions attach to folders and inherit down the tree, so you set access at the coarsest level that works and let nesting carry the rest.
In the sidebar, the + beside Folders makes a top-level folder: name it and press Enter. It starts empty, and you own it. Inside a folder, its menu and the Add row on its page make files and folders, upload, or add a connector. A name can be almost anything: spaces, capitals and other scripts are fine; only a slash, a name of just . or .., and control characters are refused.
What you upload is live immediately, and reachable by you. Widen that from the folder's access page (see the lifecycle below).
How content goes live
New content — whether uploaded here or synced from a Connection — is live the moment it lands. What decides who can see it is not a review step but the grants written at that moment:
Uploading a file grants you access to it. Connecting a source grants the readers you chose at install. Nobody else can read any of it until you widen that from its access page — which is the same mechanism that governs every other file, so there is one place to look and one answer.
Sharing outside, publishing, and public content
Someone in another organization. On a folder's access page, enter their email and Viewer or Editor. They accept it in their own organization, at the top level or in a folder they choose, and only they and their own AIs read it: not their colleagues, whatever those are granted. It can only go where nobody else there can see it. Nothing is copied, and withdrawing it takes it from their tree.
Anyone (public). The same page publishes a folder or document to the public registry. You see every file before approving, a folder holding SKILL.md is a skill, and each new version is shown and approved again. Whoever approved a version can unpublish it. An agent can only propose a publication; its person approves it.
Public content in your folders. A registry package, or a public file from GitHub, can be added to a folder you choose. It keeps up to date with each new version unless you pin it, when adding it or from its right-click, where a package can also be pinned to any approved version. Editing your copy stops the updates.