Spaces, Projects & Tasks
Organise work from broad context down to executable units.
Primitive already has organisations/scopes, projects, nested folders and tasks. The target vocabulary makes Space the durable context, Project the bounded objective, and Task the executable unit.
Think of a Space as a room for one area of life or work, a Project as something you are trying to finish in that room, and a Task as one thing somebody can actually do next.
The work model gives every conversation, document, decision, agent run and task somewhere meaningful to belong. Existing Workspace structures are real and usable; the remaining work is semantic convergence so the UI, APIs and docs use one stable Space → Project → Task mental model rather than several overlapping names.
Current implementation
Canonical Workspace includes organisations/scopes for Primitive Labs, Primitive, WhatBit and Elsewhere, plus projects, nested folders, tasks, documents, meetings and references.
- Projects and tasks are production-backed objects.
- Nested folders provide existing containment below project level.
- Meetings, documents and references already participate in the work graph.
Target semantic model
Space is the durable context boundary; Project is a bounded body of work inside a Space; Task is an executable unit. The docs treat that target as partial until the implementation vocabulary is fully converged.
Boundary
Containment is not the same thing as every useful grouping. Cross-project work can be represented by relationships or constellations without rewriting canonical parentage.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.