Resolve corresponding artifact family dependencies

docs/internal/artifacts.md

@@ -102,6 +102,10 @@ Configured sources (`narratio.artifact.*`):
   rewriting manifest state. Catalog construction iterates current
   configuration, so removed or renamed records are not advertised.
 
+`narratio.member_artifact.*` is not a runtime source family. Configuration
+resolution accepts it only in an artifact-family declaration and rewrites it
+to the corresponding configured source before this catalog is built.
+
 Prepared stable sources (`narratio.input.*`):
 
 - resolve only from the current manifest's exact prepared-input record;

docs/internal/configuration.md

@@ -129,5 +129,9 @@ therefore receive only concrete artifact maps.
 
 The catalog retains sorted family member keys plus family/character/source
 origins and the typed dependency/publish declarations for their later owners.
-It does not create a new runtime artifact type, dependency edge, or publish
-rule during this resolution step.
+`member_dependencies` add corresponding ordinary concrete dependencies, while
+the family-only `narratio.member_artifact.<family>` input form is rewritten to
+the matching ordinary configured-artifact source. The catalog records those
+resolved dependency and input identities with their declaring family and party
+member. No member-artifact source is registered as a runtime policy source.
+The typed publish declaration still does not create a publish rule here.

docs/internal/stage-analyze.md

@@ -9,7 +9,8 @@ dependency order, and safely materialize validated outputs.
 
 - ordinary configured artifacts from `pipeline.scriptorium.artifacts`; canonical
   party artifact families have already expanded into this map during
-  configuration resolution
+  configuration resolution, including corresponding member dependencies and
+  rewritten member-artifact input sources
 - optional selected artifact keys supplied through the stage environment
 - built-in, configured, extraction, and previous-session source references in
   artifact inputs