Prepare the D&D processing configuration sprint

docs/roadmap/mvp.md

@@ -263,6 +263,30 @@ application-role releases in one source repository.
   them owns their deployment.
 - Credential fields contain environment-variable names, never secret values.
   Secret delivery remains suite-level policy.
+- The standalone Narratio role owns the root pipeline document. The pipeline
+  role owns its D&D-specific imported processing, artifact, and artifact-family
+  fragments under `/usr/local/etc/narratio` and selects them through an
+  explicit ordered `configkit.imports` list.
+- Each ordinary artifact and artifact family is defined in a separate managed
+  file. Explicit imports are preferred to directory globs so removed or stale
+  files do not remain active implicitly.
+- The pipeline role manages a native `profiles/testing.yml` overlay for
+  inexpensive development and asset iteration. Production retains its
+  frontier-oriented model/profile policy; callers select the testing overlay
+  explicitly with Narratio's `--profile testing` interface.
+- Base fragments and the testing overlay contain configuration and
+  environment-variable or secret-reference names only. They never contain raw
+  credentials.
+- The D&D suite deliberately supplies Audita's complete reviewed processing
+  policy, including the current module sequence and tuning, `audita-v1`
+  output, the `https://inference.ai.rakestrawhome.com/v1` endpoint, and
+  `google/gemma-4-31b-it` for proposal and validation. Those values remain
+  inventory-overrideable and are suite policy rather than copies of upstream
+  defaults.
+- The Narratio `testing` profile selects `gemini-flash-latest` for its
+  Scriptorium artifacts and families. Audita initially uses the same endpoint
+  and models in production and testing; identical values are inherited rather
+  than duplicated in the overlay.
 
 ### Execution model