Skip to content

Architecture decision records ​

An ADR records one decision that is expensive to reverse: what we chose, why, and what would make us revisit it. They are short and never rewritten after acceptance. To change a decision, add a new ADR that supersedes the old one and mark the old one "Superseded by ADR NNNN".

Write an ADR when a choice affects more than one package, adds or removes a dependency, changes a rule in the spec, or when someone later would reasonably ask "why did we do it this way?". Do not write one for a local implementation detail.

ADRTitleStatus
0001Web only, native app on holdAccepted
0002beUI replaces shadcnAccepted
0003Package and repo slugs without &Accepted
0004Versioning strategyAccepted
0005Cloudflare primitives for files, jobs and schedulesAccepted
0006Polar deferred to milestone 5Superseded by 0010
0010Stripe Checkout for paymentsAccepted
0011Clipper app connected by API keyAccepted
0012Clipper handoff into videos and the frame boardAccepted
0013Clipper looks at keyframes (still frames), not videoAccepted
0014Clipper output modes: processed, unprocessed and markersAccepted
0007Role modelAccepted
0008Planned screens driven by a registryAccepted

Use the template. Number sequentially; never reuse a number.

Internal documentation. Not for clients.