Removed status and date from ADR

adr/ADR-001-repository-name.md

@@ -1,8 +1,5 @@
 # ADR-001: Use `ota-reference-design` as the Repository Name
 
-* **Status:** Accepted
-* **Date:** 2026-07-29
-
 ## Context
 
 The project requires a repository name that communicates its purpose clearly without tying the design to a single hardware platform, implementation language, or update framework.

adr/ADR-002-license.md

@@ -1,8 +1,5 @@
 # ADR-002: Use the MIT License
 
-* **Status:** Accepted
-* **Date:** 2026-07-29
-
 ## Context
 
 The project is intended to be an open educational and engineering reference for designing OTA update systems on embedded Linux.

adr/ADR-003-reference-design.md

@@ -1,8 +1,5 @@
 # ADR-003: Build a Reference Design, Not a Production Framework
 
-* **Status:** Accepted
-* **Date:** 2026-07-29
-
 ## Context
 
 OTA update systems differ significantly between products.

adr/ADR-004-full-system-image-updates.md

@@ -1,9 +1,5 @@
 # ADR-004: Full-System Image Updates
 
-## Status
-
-Accepted
-
 ## Context
 
 An OTA architecture must define the unit of update.

adr/ADR-005-package-based-updates.md

@@ -1,9 +1,5 @@
 # ADR-005: Package-Based Updates
 
-## Status
-
-Accepted
-
 ## Context
 
 An OTA architecture must define the unit of update.

adr/ADR-006-container-based-updates.md

@@ -1,9 +1,5 @@
 # ADR-006: Container-Based Updates
 
-## Status
-
-Accepted
-
 ## Context
 
 An OTA architecture must define the unit of update.

adr/ADR-007-independent-application-updates.md

@@ -1,9 +1,5 @@
 # ADR-007: Independent Application Updates
 
-## Status
-
-Proposed
-
 ## Context
 
 An embedded Linux device may contain applications that change more frequently than its operating system. Releasing a complete system image for every application change can tie unrelated work to the same release schedule.

adr/ADR-008-binary-delta-delivery.md

@@ -1,9 +1,5 @@
 # ADR-008: Binary Delta Delivery
 
-## Status
-
-Proposed
-
 ## Context
 
 A device may need a large artifact even though much of its content is already present in the installed version. Transferring the complete artifact can be expensive or slow on a constrained connection.

adr/ADR-009-versioned-filesystem-trees.md

@@ -1,9 +1,5 @@
 # ADR-009: Versioned Filesystem Trees
 
-## Status
-
-Proposed
-
 ## Context
 
 A software platform can be released as a complete set of files and directories without representing every release as a separate block image.

adr/ADR-010-hybrid-update-strategies.md

@@ -1,9 +1,5 @@
 # ADR-010: Hybrid Update Strategies
 
-## Status
-
-Proposed
-
 ## Context
 
 An embedded Linux device may contain a slowly changing platform, frequently updated applications, and data maintained on a separate schedule.

adr/ADR-014-trial-boot-and-confirmation.md

@@ -1,8 +1,5 @@
 # ADR-014: Trial Boot and Confirmation for System Updates
 
-* **Status:** Proposed
-* **Date:** 2026-10-05
-
 ## Context
 
 A new system image can install correctly and still fail to start or run the main application. If the new system cannot start the OTA manager, that manager cannot request recovery.

adr/ADR-015-service-checks-and-package-downgrade.md

@@ -1,8 +1,5 @@
 # ADR-015: Service Checks and Package Downgrade
 
-* **Status:** Proposed
-* **Date:** 2026-10-05
-
 ## Context
 
 An independently updated service can fail after its new package is installed. It may crash, fail to become ready, or keep running without doing its job. Restarting it repeatedly may leave the device without an essential function.

adr/template.md

@@ -1,8 +1,5 @@
 # ADR-NNNN: Decision Title
 
-* **Status:** Proposed
-* **Date:** YYYY-MM-DD
-
 ## Context
 
 Describe the problem or architectural question that requires a decision.