ADRs 0091 and 0092; issues 026 and 070 resolved; designs 18 and 24 amended

2026-09-21 17:50:41 +02:00
parent ffb7fa52ec
commit 16442ecd23
9 changed files with 183 additions and 8 deletions
@@ -1,9 +1,9 @@
 ---
-status: located
+status: resolved
 opened: 2026-09-01
 located-in: [mesh-control]
-fixed-by: partly — mesh-controller f5b03e1 declares the data directories; the gate refusing a container mount the module never declared (53eb000) was withdrawn in 83c6a2f and nothing replaces it
-amended-design:
+fixed-by: mesh-controller f5b03e1 (the fourteen declared); ADR 0091 and mesh-controller feat/multiple-fixes (the check, back, with the three declarations — the socket by capability, the operator's by accesses)
+amended-design: 03-DESIGN/01-to-be/18-building-a-module.md
 ---

 # 026 — The data directories are mounted and never declared
@@ -0,0 +1,14 @@
+# Diagnosis — 2026-09-21
+
+1. The catalogue was read again for mounts no resource declares: twenty-four remained, in two
+   kinds only. Nine media modules mount the operator's library, and every one of those paths is
+   already in the module's `accesses` — the vocabulary [ADR 0051](../../02-DECISIONS/0051-shared-data-is-the-operators.md)
+   gave exactly this. Four modules mount the container runtime's socket, and every one of them
+   declares the `container-runtime` capability.
+2. So the field the report said would have to be invented already exists twice over, and the
+   check that was withdrawn needed only to read both: an access is a declared path, and a
+   capability declares the facility it grants.
+
+**Located in:** the catalogue's parser. The check is back, refuses an undeclared mount naming the
+path and the three remedies, and a test parses the whole catalogue. Decided in
+[ADR 0091](../../02-DECISIONS/0091-a-mount-is-declared-three-ways.md).