ADRs 0044 and 0045 — the module design, closed; 011 graduates

011 opened asking what a graph deletes and found the graph already existed. The
work became design, worked through twenty cases and one provider in full. Two
decisions close it.

0044 — a module declares presence, instantiation and exclusion. Two kinds of
edge because a game wanting a database is not a game wanting postgres to exist:
one creates something per consumer, carries credentials back, can be revoked,
and leaves the provider holding state. Names are concrete unless providers are
genuinely substitutable — `terminal` passes, `database` fails, and the adapter
is what creates an interface. Where there is no contract there is a tag, which
describes and does not bind. Exclusion is a third relation and is not derivable.
A node provides names too, which makes capability checking stop being a separate
mechanism and makes the host's detection an input to resolution. Constraints,
never placement. Scope decides which provider and the binding is written down
and sticky, in a place that follows the scope. And there are three entities, not
two — the assignment carries what belongs to neither end, which is what
node-agnostic modules ran out of.

0045 — a context owns its store, exclusively. No shared writes and no read roles
on another context's store, because reading couples you to its layout just as
firmly and invisibly. The unit is the CONTEXT, not the process: a board showing
the mesh's own data is the mesh showing its own data. Asking or subscribing is
derived from ADR 0036 rather than chosen. And it is the first clear list of what
the design removes: grant kinds, table ownership, cross-context migration
ordering, and a class of permission modelling.

0017 is superseded rather than narrowed — its text unchanged, its status
changed. Folders assert relationships where edges record them, and the domain
module goes with it.

Left explicitly undecided in both: what a resolver delegates rather than
reimplements, how many instances a module should have, and what a provider hands
back.

01-RESEARCH/011-the-module-graph/00-overview.md

@@ -1,6 +1,11 @@
 ---
-status: active
+status: graduated
 initiated: 2026-08-25
+became:
+  - 02-DECISIONS/0044-a-module-declares-presence-instantiation-and-exclusion.md
+  - 02-DECISIONS/0045-a-context-owns-its-store.md
+  - 03-DESIGN/01-to-be/06-the-control-plane.md
+  - 03-DESIGN/01-to-be/07-the-substrate.md
 touches:
   - 02-DECISIONS/0002-everything-is-a-module.md
   - 02-DECISIONS/0017-modules-outside-the-core-are-grouped-by-domain.md