What is Project Brain?
Project Brain is the long-form knowledge base attached to every project. It's your long-term memory — where you store the "why" and "how" so you don't lose context over time.
Context is the most expensive thing to rebuild. Brain exists to ensure that when you come back to a project after a month, you're not starting from scratch.
Why Brain exists
Ideas are perfect for capturing fragments and tasks. But projects also need a narrative: constraints, vision, architecture, and the "big picture". Brain keeps that logic in one place.
What belongs in Brain
Vision & Strategy
What outcome are we chasing? Who is it for? What is the core problem we solve?
Technical Specs
Architecture decisions, API design, and constraints that dictate how we build.
Tradeoffs
"We chose X because Y." Documenting the decisions that usually get lost in chat history.
Checklists
Release steps, deployment notes, and the "Definition of Done".
A high-fidelity template
Brain vs Ideas
If it's an actionable item or a quick note, create an Idea. If it's the context that makes the idea meaningful, it belongs in the Brain.