use cases
architecture decisions need rationale. 'why did we choose postgres?' jottie captures decisions and their reasoning. years later, the context is still searchable.
use cases
powered by jottie
capture decisions
preserve rationale
find context later
drag notes around, search, and click to explore
why this works
capture decisions
preserve rationale
find context later
tradeoffs documented
examples
see how others use jottie for use cases. try these prompts to get started.
try these
details
note architecture decisions with context - what, why, alternatives considered. jottie indexes everything. search later to understand past decisions.
capture decisions
include rationale
searchable history
how it works
details
architecture decisions without rationale cause endless re-litigation. searchable decision records end the 'why did we do this?' conversations.
why jottie for architecture
architecture decisions without rationale cause endless re-litigation. searchable decision records end the 'why did we do this?' conversations.
questions
is this like adrs?
similar purpose, simpler format. you can use adr structure in your notes.
can the team access decisions?
personal notes for now. share via export for team reference.
does it integrate with code?
not directly. reference decisions by name in code comments.
start with a single note, then use search or chat to pull the context back instantly.