Approve 0049-0053; drop a to-be item superseded by ADR 0044

The 'domain grouping' item cited ADR 0017 as live guidance. 0044 superseded it -- there is no domain module to group into, so there is no domain list to settle.
2026-08-27 01:00:29 +02:00
parent ccbbfa9c8a
commit ef5dd0751b
6 changed files with 10 additions and 8 deletions
@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: accepted
 date: 2026-08-27
 deciders: jochen
 reconstructed: false
@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: accepted
 date: 2026-08-27
 deciders: jochen
 reconstructed: false
@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: accepted
 date: 2026-08-27
 deciders: jochen
 reconstructed: false
@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: accepted
 date: 2026-08-27
 deciders: jochen
 reconstructed: false
@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: accepted
 date: 2026-08-27
 deciders: jochen
 reconstructed: false
@@ -25,6 +25,8 @@ document is written and this one's status becomes `implemented`.
  decides the decomposition; `connectivity` is the first written in full
  ([`08`](08-connectivity.md)) and the others do not exist yet. The work breakdown says in what
  order they are needed.
- **Domain grouping outside the core.** [ADR 0017](../../02-DECISIONS/0017-modules-outside-the-core-are-grouped-by-domain.md)
-  settles the principle and explicitly does not settle the domain list. That is a research
-  effort, not a design document, until it concludes.
+- ~~**Domain grouping outside the core.**~~ **Not needed.**
+  [ADR 0017](../../02-DECISIONS/0017-modules-outside-the-core-are-grouped-by-domain.md) is
+  superseded by [ADR 0044](../../02-DECISIONS/0044-a-module-declares-presence-instantiation-and-exclusion.md):
+  there is no domain module to group into, so there is no domain list to settle. Relationships
+  are edges, and grouping is a tag and a query.