01 · Action before architecture
Begin with something you want to move forward. Add structure only when the work asks for it.
About ActionDrivenNote
Work produces knowledge. The system should notice.
ActionDrivenNote is built around a simple idea: the best notes often appear while you are trying to move something forward.
Why it exists
Less filing. More continuity.
Task managers are good at showing what remains. Note-taking tools are good at storing what has been written. The gap appears in the middle, where research, decisions, drafts, and new actions are created as part of doing the work.
ActionDrivenNote keeps that middle intact. Every action can become a place to think. When the action is complete, you decide whether its context should fade away or become part of the knowledge you keep.
02 · Context belongs with the work
Research, drafts, decisions, and next steps should not drift into unrelated folders and tabs.
03 · Completion should not erase learning
Most tasks can disappear. The few that contain lasting value should remain understandable later.
04 · AI should enter with permission
Agents should work with selected context through an explicit, reviewable authorization flow.
The product is in beta