Plan D&D S3 storage and publishing

docs/roadmap/mvp.md

@@ -370,6 +370,15 @@ application-role releases in one source repository.
 - The Narratio `testing` profile keeps the Notarius stage enabled and inherits
   the same D&D pipeline and extraction profile as production until a distinct
   testing extraction policy is selected.
+- The D&D suite selects its Backblaze-compatible S3 archive, typed
+  `OBJECT_STORAGE_KEY_ID` and `OBJECT_STORAGE_KEY` references, maximum S3 audio
+  caching, run publication, human-facing transcript and artifact outputs, and
+  cleanup of successfully published workspace state. Feature 0015 owns the
+  exact overrideable defaults and publication set.
+- Accepted Notarius lane outputs remain addressable inside Narratio as
+  `narratio.extraction.<output_key>` sources. Future analyze-stage Scriptorium
+  artifacts may consume those sources directly; publishing an extraction lane
+  to a stable remote destination is an independent policy choice.
 
 ### Execution model
 
@@ -389,7 +398,7 @@ later design decision changes them:
 - `/usr/local/etc/notarius/pipelines` for suite-owned imported Notarius
   pipeline definitions
 - `/usr/local/etc/scriptorium/config.yml` for Scriptorium configuration
-- `/usr/local/etc/narratio/secrets` for future restricted credential material
+- `/usr/local/etc/narratio/secrets` for suite-managed restricted credentials
 - `/usr/local/share/narratio/campaigns` for version-controlled campaign data
 - `/usr/local/share/narratio/prompt-library` for version-controlled prompts
   and schemas