Appearance
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.
| ADR | Title | Status |
|---|---|---|
| 0001 | Web only, native app on hold | Accepted |
| 0002 | beUI replaces shadcn | Accepted |
| 0003 | Package and repo slugs without & | Accepted |
| 0004 | Versioning strategy | Accepted |
| 0005 | Cloudflare primitives for files, jobs and schedules | Accepted |
| 0006 | Polar deferred to milestone 5 | Superseded by 0010 |
| 0010 | Stripe Checkout for payments | Accepted |
| 0011 | Clipper app connected by API key | Accepted |
| 0012 | Clipper handoff into videos and the frame board | Accepted |
| 0013 | Clipper looks at keyframes (still frames), not video | Accepted |
| 0014 | Clipper output modes: processed, unprocessed and markers | Accepted |
| 0007 | Role model | Accepted |
| 0008 | Planned screens driven by a registry | Accepted |
Use the template. Number sequentially; never reuse a number.