Note editor
The note editor is where user-authored research knowledge lives in a project. Use it for observations, synthesis, source notes, unresolved questions, and reusable context.
What belongs in notes
Good notes usually contain:
- claims you want to reuse
- summaries you have verified
- comparisons across sources
- questions to revisit
- decisions and rationale
- links or mentions to relevant project material.
Do not leave important work only in chat. Chat is useful for exploration, but notes are easier to find, organize, mention, and build on later.
Note anatomy
| Part | Role |
|---|---|
| Title | The main identifier for search, mentions, and navigation. |
| Body | The research content. |
| Headings | Internal structure for scanning and reuse. |
| Mentions | Links to sources, notes, or project objects used as context. |
| Attachments or images | Visual support when needed. |
Autosave and persistence
Atlas notes should preserve changes as you work, but treat long-form writing with the same care you would in any web editor. Keep titles specific, avoid leaving critical information in an untitled note, and pause after major edits so the save state can settle.
Notes as context
Mention notes in chat when you want Atlas to use your own synthesis, definitions, or prior decisions. This is different from citing a source: a note is user-authored context unless it links back to source evidence.
Notes versus sources
| Use a note when | Use a source when |
|---|---|
| You are writing your own interpretation. | You need Atlas to process original material. |
| You need a reusable working summary. | You need citations to the original material. |
| You are tracking decisions or questions. | You want search, maps, or summaries from imported content. |