Goals & Projects
Goals answer “why are we doing this?” Projects answer “what concrete deliverable are we organizing around?” In Paperclip, goals form the higher-level intent tree, while projects group work, workspace…
Goals and Projects
Goals answer “why are we doing this?” Projects answer “what concrete deliverable are we organizing around?” In Paperclip, goals form the higher-level intent tree, while projects group work, workspaces, and runtime behavior around a deliverable.
---
At a Glance
| Concept | Use it for | Key fields | Notes | |---|---|---|---| | Goal | Company mission, team objective, or agent/task objective | title, description, level, status, parentId, ownerAgentId | level defaults to task; status defaults to planned | | Project | A deliverable with linked goals and workspaces | name, description, status, goalId / goalIds, leadAgentId, targetDate, env, executionWorkspacePolicy | goalIds is preferred; goalId is kept in sync for legacy callers | | Workspace | A repository or local folder attached to a project | name, sourceType, cwd, repoUrl, repoRef, defaultRef, visibility, runtimeConfig, isPrimary | The first workspace becomes primary automatically |
All of these endpoints are company-scoped. If you cannot access the company, you cannot list or mutate its goals or projects.
---
Goals
Goals are the planning layer. They are useful when you want to express strategy, break objectives into sub-goals, or attach ownership to a specific agent.
Goal levels are: