Why Can Notes, Actions, and Scenes Be Interchanged?
Behind this design lies an advanced product philosophy that closely mirrors how humans actually think: Progressive Evolution and Emergence of Thought.
Our thinking process itself is not linear or predetermined. The birth of an idea often starts from a vague notion.
1. Starting as a "Note" — Capturing Fleeting Inspiration
Initially, you might just have a simple idea or record. For example: "I should be able to create an automated user comment analysis workflow." At this point, it's best suited to exist as a Note. It's a free, unstructured content carrier whose core task is recording and preserving.
2. Evolving into an "Action" — From Thought to Executable Workflow
After repeatedly performing the "analyze user comments" task, you gradually summarize a fixed set of steps (SOP). That former "Note" has evolved from a simple idea into a structured set of instructions. At this point, you just need to switch its type to "Action" with one click.
Why this design? It significantly lowers the barrier and friction of creation. You don't need to think about whether an "idea" will become a complex workflow at the moment it's born. Just record it first. When it matures, the system allows you to "promote" it, turning static thinking into a reusable, executable dynamic workflow.
3. Evolving into a "Scene" — From Workflow to Immersive Environment
Similarly, a "Note" that initially records project background, goals, and core materials—when you find yourself needing to have continuous, in-depth conversations with AI around these core contexts, you can switch it to a "Scene".
Why this design? This makes any knowledge block a potential "context anchor". A simple project introduction note can instantly be "activated" into a focused, independent AI collaboration environment with long-term memory.
Summary
The essence of this design philosophy is empowerment and flexibility.
It acknowledges the non-linearity and emergence of thought, allowing users at any time, based on evolving needs, to give any "knowledge block" new life and roles—from static records, to dynamic workflows, to immersive environments.
This represents profound respect for the user's creative process.