This month's special: Save ¥30 on templates|Discount applied automatically at checkout|Only 26 days left 06:46:22
This page targets searches around notes systems, knowledge management, and second brains. It explains why notes need roles, why they reconnect to areas, projects, and tasks, and why they stay worth revisiting.
6 note roles
Different content plays different roles
Topic clusters
Repeated outputs fit topic notes well
Multi-linked
Notes can connect to areas, projects, and tasks
The left side explains note structure. The right side hints at topic notes, connections, and revisit flows.
Knowledge Assets
This page should show that FLO.W manages not note count, but how notes are organized, aggregated, and reused.
Idea
How
Topic note
This layer shows the top navigation, the main views, and the most-used entry points before going deeper.
6 note roles
Topic notes
Revisit
Core tension
Information keeps coming in, but ideas, references, and project records are still hard to retrieve when needed.
Practical problem
Many note tools only collect input. Without roles and relationships, content grows more scattered over time.
Positive return
When notes can be reorganized by role, topic, and context, knowledge starts to feel useful again.
The page explains how this module is organized first, then shows how it connects to the rest of FLO.W and what role it carries inside the wider system.
Ideas, methods, logs, references, and topic notes each have a role, which makes every note easier to understand.
When travel logs, study notes, or project reviews keep growing, one main note with child notes stays cleaner.
Notes can connect to primary areas and also to secondary areas, projects, or tasks, which makes reuse easier.
Attention level, completion, and random revisit help decide what deserves more energy and what can rest.
The module home gives the whole picture first. The pages below then expand into types, scenarios, and design details.
A third-layer entry for showing the six note roles and what each one handles.
Best for showing how one main note gathers repeated outputs and child notes.
Useful for showing deeper pages inside the note module for different recording scenarios.
Parent-child links, attention level, completion, and relations work best after the full module view.
Quick capture and outside material land first. Preservation comes before organization.
The goal is to place content where it belongs, not to build an overcomplicated hierarchy.
When the next project, article, or review starts, old notes continue providing context.
FLO.W’s notes system is built for long-term accumulation. It places quick capture, topic notes, project records, and outside resources on one knowledge map.
The reader can understand the problem this module solves, where it fits inside FLO.W, and which docs or cases are worth opening next.