What Can Be Proposed

A proposal can represent almost any structural change to your data folder—from a single task to a complete reorganization of your areas. This chapter shows what’s possible.

Overview by Entity

The following table shows which actions can be proposed for each entity:

What the Actions Mean

Create—the entity doesn’t exist yet and is newly created. For new tasks, projects, milestones, and folders, the AI can specify the right place in the hierarchy directly.

Change—existing fields are updated: for example, title, status, due date, tags, description, or success criteria.

Move—the entity changes its place in the hierarchy. A task can move from the Inbox into a project, for example, or a project from one area to another.

Rename—applies to folders, areas, and view folders; these have their own rename action because their internal identifier changes as well.

Delete—the entity is removed, just as when you delete it by hand: On the Mac, tasks, projects, milestones, areas, and views go to the Trash. When a folder is deleted, its projects and standalone tasks move to the area; when a view folder is deleted, its views move to the parent folder.

Combinations in One Proposal

A single proposal can combine actions across several entities and types. A typical example: The AI creates a new tag and a new project at the same time, moves three tasks from the Inbox there, and sets their due dates—all in one proposal that you approve or refine with a click.