Discovery to Brain
One of the highest-value MindMux workflows is turning exploratory thinking into durable project knowledge.
Typical pattern
- Start a session around a product or technical question.
- Explore options, constraints, and tradeoffs in chat.
- Distill stable conclusions into root docs or pages.
- Leave the project in a better documented state than it was before.
Best use cases
This workflow is especially strong for:
- project framing
- architecture exploration
- design rationale capture
- research synthesis
- documenting why a choice was made
What should become a root doc
Use root docs when the result updates the project-wide shared truth, such as:
- background and positioning
- overall architecture
- key flows
- stack choices
- roadmap shape
What should become a page
Use pages when the result is about a specific concept, decision, person, or reference that should stand on its own and keep an evolution history.
A page can be draft while it is taking shape, active once it represents current project truth, and archived when it becomes outdated but still has historical value. These are lifecycle states of the same page, not separate storage layers.
Success criteria
A good discovery session should reduce future re-explanation. If the next contributor still has to ask the same setup questions from scratch, not enough of the result made it into the brain.