Project structure
A project is the top-level container for a research context in Atlas. It groups the original material, your notes, AI-generated views, and conversations for one topic or deliverable.
Project artifacts
| Artifact | Role |
|---|---|
| Source | Original material Atlas can process, search, summarize, map, and cite. |
| Note | User-authored research knowledge, synthesis, and follow-up work. |
| Chat | A conversation for asking grounded questions against project context. |
| Knowledge map | A visual structure generated from source material. |
| Semantic map | A broader landscape view across project items and concepts. |
| Summary | A compact reading or triage artifact derived from project material. |
| Citation | A verification link back to source evidence. |
Isolation
Project material belongs to the project where it was created or imported. Before adding sources or asking questions, check that the correct project is open.
This matters because retrieval, citations, maps, and summaries depend on project context.
Naming projects
Use names that describe the actual research work:
- "RAG citation trust model"
- "Q3 customer interview synthesis"
- "Literature review: visual knowledge maps"
- "Competitor docs analysis"
- "Thesis chapter 2 sources".
Avoid names like "Test", "New project", or "Research" unless the project is disposable.
Project hygiene
Keep a project focused enough that its sources and notes are relevant to the same research question. If two topics need different evidence bases, split them into separate projects. If they need to be compared, keep the comparison in a note or synthesis inside a broader project.
Mental model
Sources are the evidence base. Notes are your authored layer. Chat is the question-answering interface. Maps and summaries are generated reading aids. Citations connect generated claims back to evidence.