Projects
A project in NEXUS is the identity of a working folder — the real, normalized path a session works in. It is the thing pinned rules, data mappings, and project-scoped memory attach to, and it is deliberately independent of any workspace: the same folder is the same project no matter which workspace, session, or agent touches it.
There is no project editor and no project browser. Projects surface through what they carry:
| Surface | What you see |
|---|---|
| The Pinned Memory panel | The resolved project's rules and data mappings, under the Project scope chip. |
| An agent's Memory card | A Project bucket in the Recall by Scope counts. |
| The project folder itself | Committed exports under .chainabit/memory/ — rules.md and data-map.md — folded into CLAUDE.md and AGENTS.md. |
In this guide
- Creating — how a project record comes to exist (you never create one explicitly), the naming default, and the identity rule.
- Scope & Membership — which workspaces a project is linked to, and what travels with the project rather than the workspace.
Where to go next
- Project Model — project vs workspace vs repository, the three overlapping nouns.
- Pinning & Promotion — the flow that writes into a project's memory.
- Paths & Credentials — the
.chainabit/directory a project's committed files live in.