Sharing a folder with an AI agent should be as understandable as sharing it with a colleague. The owner chooses a recipient, grants an exact scope, and can later revoke it. The hard part is preserving that simplicity across local devices, cloud services, and temporary agent sessions.

Folderbase calls this model a Live Folder: an ordinary folder made versioned and shareable through explicit grants, without turning a URL into a bearer credential or copying the files into a separate collaboration product.

The recipient grant is the source of authority

A share link should locate a Folderbase, folder, object, or view. It should not carry permanent authority by itself. Access belongs to a named or otherwise explicit recipient grant that can be audited and revoked.

That distinction prevents forwarded links from silently widening access. It also gives every device and agent session a clear principal to inherit from.

Humans and agents follow the same ceiling

An agent working for a recipient should never receive more access than the recipient has. It cannot mint stronger credentials, manage sharing, or infer authority from a relationship graph. Its session is bounded by the same Folderbase scope and an even narrower task grant when appropriate.

This creates permission parity without pretending agents and humans are identical. Agent sessions can also be limited by time, tools, tokens, and a pinned input version.

Sharing must preserve local-first behavior

A Live Folder remains directly usable on authorized devices. Sync transfers immutable objects and reconciles versions, while the local workspace continues to work with normal applications. Keep Local and Archive are explicit states; active work should never disappear because a cloud optimizer silently evicted it.

Conflicts are preserved rather than overwritten. Text conflicts can be reviewed, binary sides can both survive, and clean-device restoration should reproduce every authorized byte.

Revocation stops access without deleting the source

When a grant is revoked, the recipient and sponsored sessions lose future access. The owner's source data remains intact, as does the audit history explaining what was previously shared and changed.

Any unmerged agent proposal can remain a reviewable Change Set without gaining permission to publish. This separates preservation of work from authority to apply it.