Compose production modules through family registrars

docs/internal/overview.md

@@ -22,7 +22,7 @@ a sorted set of artifact lanes before the runner constructs any stage module.
 | Package | Implemented responsibility |
 | --- | --- |
 | `cmd/notarius` | Executable entry point and process exit delegation. |
-| `internal/cli` | Command parsing, config discovery, production registration, prompt asset collection, LLM client construction, reference materialization, workspace collaborator setup, durable writes, and user-facing results. |
+| `internal/cli` | Command parsing, config discovery, package-family registrar invocation, LLM client construction, reference materialization, workspace collaborator setup, durable writes, and user-facing results. |
 
 ## Core Packages
 
@@ -75,7 +75,19 @@ Concrete validators live under `internal/validators`. Generic packages provide
 unconditional test decisions, JSON syntax validation, and JSON Schema
 validation. D&D spell packages provide shape, source-reference, and
 source-relatedness decisions, with `spellpayload` holding their shared parser
-and lookup helpers. Production chain composition is owned by `internal/cli`.
+and lookup helpers.
+
+Production composition is grouped behind package-family registrars while the
+implementations remain in their current stage-oriented packages:
+
+| Package | Implemented responsibility |
+| --- | --- |
+| `internal/modules/generic/register` | Registers domain-neutral chunk, merge, normalize, output, and validator implementations. |
+| `internal/modules/seriatim/register` | Registers the Seriatim input adapter. |
+| `internal/modules/dnd/register` | Registers D&D modules, validators, default validator policy, and prompt/schema assets. |
+
+The CLI allocates the framework registries and asset registry, then invokes
+these registrars in generic, Seriatim, and D&D order.
 
 Implementation details for all production extensions are in
 [Module Internals](modules.md).