Where things live

Every task, document, and folder in Dhanu belongs to exactly one of two homes. Not both, not none. Picking the right one decides who can see the work and who can change it.

The two homes

Personal is yours. Drafts, scratch work, anything you are not ready to share. Nobody else in the workspace sees it.

A project is a boundary around a piece of work, with its own member list. A client engagement, a launch, an investigation, or the standing reference material a group keeps coming back to. See What a project is.

Choosing between them

Ask who should see it.

• Only me, for now → personal
• A specific group of people → project

Moving something later is fine. The point is that at any moment there is one answer to “who can see this”, not a pile of overlapping permissions to reason about.

What follows the scope

Because the home is a property of the thing itself, everything downstream inherits it. A task in a project produces documents in that project. An image or spreadsheet the AI makes inside a task belongs wherever the task belongs. You do not set permissions separately on each artifact, and they cannot drift apart.

Two deliberate exceptions:

Templates and workflows are never project-scoped. They stay personal so that a house format does not vanish when a project is archived.

Brain pages scope on their own terms. A page can be restricted to certain projects or certain AI staff regardless of where a task lives, because a policy is not a file, see What Brain is.

Deleting

Files and folders deleted from either home go to the trash for thirty days, and come back to the same place when restored, see Trash and restoring.

Next

What a project is covers the shared home in detail, including the roles inside it. Inbox covers how work finds you once it has a home.