Give 0115 a home, and match its batch's status

Both repository checks fail on main. 0115 is cited by no design, and it is marked accepted while resting on 0112, which is proposed. Design 27 already states the rule the record decides — "a module is assigned at most once to a node, and that pair is the assignment's identity" — so it is the home, and now says so. And 0112, 0113, 0114 and design 27 are all proposed: the batch is under review, so the record is too. Promoting 0112 instead would be marking a record accepted to satisfy a check, which check_rests_on names as a failure this repository already made once.
2026-09-26 19:03:14 +02:00
parent 3950c2b75d
commit 0af6479b2c
3 changed files with 3 additions and 1 deletions
@@ -5,6 +5,7 @@ code: []
 updated: 2026-09-26
 decisions:
  - 02-DECISIONS/0112-a-module-definition-names-no-node-mesh-or-path.md
+  - 02-DECISIONS/0115-one-assignment-of-a-module-per-node.md
  - 02-DECISIONS/0113-the-vault-makes-every-secret.md
  - 02-DECISIONS/0114-a-shared-credential-rotates-over-two-credentials.md
  - 02-DECISIONS/0110-a-seat-is-a-module-assignment-from-a-closed-set.md