Decision records¶
These architecture decision records (ADRs) explain choices that a later change has to respect, and the alternatives each one beat. The pages elsewhere in this manual describe how the system works now; a record here says why it works that way.
Each file is named for the date the decision was made. A record isn't edited once it's Accepted. A changed decision gets a new record that supersedes the old one.
| Date | Decision | Status |
|---|---|---|
| 2026-07-13 | Delegate App approvals through a required check | Accepted |
| 2026-07-13 | Store webhook work before acknowledging it | Accepted |
| 2026-07-15 | Apply schema changes only through an explicit migrator | Accepted |
| 2026-08-17 | Build the runtime image on Debian slim | Accepted |
| 2026-08-17 | Release every main commit from its CI run | Accepted |
| 2026-10-11 | Keep the published result on a scheduled recheck | Accepted |
| 2026-11-02 | Bound discovery optimizations without weakening evidence | Accepted |
| 2026-11-05 | Link bounded request traces to a reconciliation summary | Accepted |
| 2026-11-05 | Reuse authenticated, version-matched Debian sources | Accepted |
These first five were written in October 2026 to record decisions already in effect. Their dates come from the commits and pull requests that made each decision. Each record states the decision as it stands now, including later refinements, and its Implementation row names the pull requests that added them.