Short records of design calls that shaped stube. Each ADR captures one question, the answer, why we chose it, and what it cost — the same spirit as Michael Nygard's ADR template, trimmed to one screenful so they actually get written.
Read in order if you're new; the early decisions set the noun set the later ones inherit.
| # | Decision |
|---|---|
| 0001 | Resume keys live on the parent under explicit names, not on the child |
| 0002 | Conversation state must round-trip through EDN |
| 0003 | :children materialises eagerly; :call pushes a stack frame |
| 0004 | :app is a per-kernel value; :principal is fixed at mint time |
New ADRs should follow the same shape — Context, Decision, Consequences. Number sequentially. Don't rewrite history: when a decision is reversed, add a new ADR that supersedes the old one and link both directions; the old file stays as a record of how we used to think.
Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |