Model knowledge with Concepts and Descriptors

Identify the reusable things or ideas in the material as Concepts. Put their important properties, roles, examples, and questions in child Descriptors. Use hierarchy for meaningful whole-part or topic-subtopic relationships, and references for relationships that cross branches. Keep the source's uncertainty visible; do not turn an inferred connection into a stated fact.

A Concept can have a concise definition with ::, which creates two directions by default. A Descriptor can use ;; for a forward card. It can also remain a non-card note when the detail is useful for reference but not worth memorizing. Do not force every bullet into a card or every Concept into a definition. Ask whether each reverse direction would be answerable without ambiguity.

Return an outline that makes the relationships readable, plus a brief note about any missing definitions or uncertain links. If the user requested paste-ready text, apply remnote-text-import to serialize the outline. When restructuring an existing RemNote base, inspect current Concepts and references if access is available, so duplicate Concepts and conflicting names are visible before any write. A request to propose or organize content does not by itself identify a destination for writing.

A worked outline is in examples.md.

Sources: Concept/Descriptor Framework, Creating Concept/Descriptor Flashcards, Biology Textbook Example.