Document workload-oriented LLM profile deployment

docs/internal/modules.md

@@ -17,8 +17,10 @@ accepted reference slots. The execution class states whether a module is
 `deterministic` or `llm_backed`; registries retain it for catalog inspection and
 resolved-pipeline debug data without constructing the module. The framework
 uses the declaration to resolve a configured binding before it builds the
-implementation. Profile inheritance and deterministic-profile validation are
-not implemented at this boundary yet.
+implementation. After selection, the resolver applies profile inheritance only
+to bindings whose declared execution class is `llm_backed` and rejects a
+binding-specific profile on a deterministic module. The user-facing precedence
+contract belongs in [Configuration](../config.md#pipelines).
 
 Implementations that accept options must provide both an option validator and
 a builder. The validator is used while resolving configuration; the builder
@@ -51,7 +53,7 @@ Production composition is intentionally split by family:
 - The Seriatim registrar provides the transcript input adapter. Its external
   input behavior is defined by the [Seriatim contract](../integrations/seriatim.md).
 - The D&D registrar provides its codecs, extractors, mergers, normalizers,
-  validators, prompt assets, and default chains. Its behavioral conventions
+  validators, prompt assets, fallback profile asset, and default chains. Its behavioral conventions
   are documented in [D&D Module Internals](dnd.md).
 
 The CLI owns the composition that invokes these registrars. A module package