Features
Decisions
A log of the important choices made during the project — and why they were made.
Why keep a decision log?
Every project is full of decisions: why PostgreSQL instead of MongoDB, why REST instead of GraphQL, why this architecture instead of that one. These decisions make sense when they're made — but six months later, nobody remembers why.
A decision log captures the what and the why at the moment it's decided. This prevents your team (and your AI) from revisiting the same debates over and over.
What a decision looks like
Example decision
Use PostgreSQL over MongoDB
We will use PostgreSQL as the primary database for all structured data.
Our data has clear relationships (users → orgs → projects → tasks). SQL joins are exactly what we need. MongoDB's flexible schema would add complexity without benefit.
How decisions get recorded
AI records decisions automatically during work sessions when it makes or observes an important choice. You can also add decisions manually.
- 1Go to the Decisions tab in your project
- 2Click Add decision
- 3Write a short title — make it clear what was decided
- 4Describe what was decided and why
- 5Save — it's now part of the project memory