diff --git a/docs/04-starting-an-updated-system-or-service.md b/docs/04-starting-an-updated-system-or-service.md
index 380c619..e7de34d 100644
--- a/docs/04-starting-an-updated-system-or-service.md
+++ b/docs/04-starting-an-updated-system-or-service.md
@@ -179,7 +179,18 @@ For example, version 2 may change a database into a format that version 1 cannot
 
 The update design must keep data compatible, provide a tested way to restore it, or define another recovery path. The same question applies to configuration and changes made by package installation scripts.
 
-## 9. What Comes Next?
+## 9. Related Architecture Decisions
+
+These Architecture Decision Records (ADRs) explain when to choose the approaches used in this chapter:
+
+| Question | Further reading |
+|---|---|
+| When should the software system be updated as one image? | [ADR-004: Full-System Image Updates](../adr/ADR-004-full-system-image-updates.md) |
+| When do independent packages fit a stable system platform? | [ADR-005: Package-Based Updates](../adr/ADR-005-package-based-updates.md) |
+| When should a new system get a trial boot before it is confirmed? | [ADR-014: Trial Boot and Confirmation for System Updates](../adr/ADR-014-trial-boot-and-confirmation.md) |
+| When should a failed service update trigger downgrade and an update lock? | [ADR-015: Service Checks and Package Downgrade](../adr/ADR-015-service-checks-and-package-downgrade.md) |
+
+## 10. What Comes Next?
 
 Both examples follow the same pattern: start the new version, check its required functions, then keep it or recover. They use different mechanisms because a system boot and a service restart fail in different ways.