FlowJoe is easier once you stop treating it like a folder app or a linear note app. Three ideas do almost all the work.

​
Structure

The tree is structure: roots, child nodes, multi-select, status, themes, locks, and private nodes. Structure answers where does this belong? and how does this branch relate to that one? A node is not just a label. It is a container that can hold meaning and references.

​
References

The gallery on the selected node is references: images, audio, video, documents, URLs, embeds, stacks, tags, and editable workbenches (spreadsheets, rich documents, calendars). References answer what am I looking at, listening to, or citing while I work here?

​
Meaning

Meaning sits above raw material:
  • Per-node notes and summaries
  • Per-slot notes
  • Tags that cut across the flow
  • The context you deliberately share with Joe
Meaning answers what does this mean for the project? — not only what files live here?

​
Why keep them separate

Many tools collapse everything into one list or one canvas. FlowJoe keeps structure and visual reference strong on purpose, then bridges them with selection (pick a node → see its gallery) and with Joe (who can use both when you allow it).