Plan D&D asset deployment

docs/roadmap/mvp.md

@@ -186,15 +186,39 @@ application-role releases in one source repository.
 
 - The pipeline role installs Narratio's PromptKit-compatible prompt library
   from the `narratio-prompts` Git repository. The Scriptorium role owns its
-  native prompt, profile, and schema directory configuration, while the
-  pipeline role owns populating those locations with suite integration
-  content.
+  native prompt and schema directory configuration, while the pipeline role
+  owns populating those locations with suite integration content.
 - The upstream repository is
-  `https://gitea.maximumdirect.net/eric/narratio-prompts`.
-- For the MVP, the pipeline role tracks and pulls the latest upstream commit.
+  `https://gitea.maximumdirect.net/eric/narratio-prompts.git`.
+- The repository is checked out at
+  `/usr/local/share/narratio/prompt-library` by default. Scriptorium's prompt
+  and schema directories are the checkout's `prompts/` and `schemas/`
+  subdirectories.
+- The repository does not currently contain execution profiles. The pipeline
+  role does not set Scriptorium's profile directory until a later suite-policy
+  feature selects and deploys profiles.
+- For the MVP, the pipeline role tracks and pulls the repository's `main`
+  branch. The origin, revision, and checkout root are configurable, and a
+  caller may select an immutable commit when required.
 - Pinning the prompt library to a version or release is deferred until the
   upstream repository provides versioned releases.
 
+### Campaign registry content
+
+- The pipeline role checks out the `campaigns` Git repository directly into
+  Narratio's campaign registry root. The upstream repository is
+  `https://gitea.maximumdirect.net/eric/campaigns.git`.
+- The default campaign root remains
+  `/usr/local/share/narratio/campaigns`, and the pipeline role passes that same
+  value to the Narratio application role.
+- For the MVP, the pipeline role tracks and pulls the repository's `main`
+  branch. The origin, revision, and campaign root are configurable, and a
+  caller may select an immutable commit when required.
+- Both asset checkouts are root-managed and remotely authoritative. Operators
+  may read the content but do not edit it on the managed host. Ordinary Git
+  module convergence owns tracked-content updates; the role does not maintain
+  separate revision state or purge untracked files.
+
 ### Accounts, ownership, and operator access
 
 - The standalone Narratio role creates a dedicated system `narratio` user and
@@ -257,6 +281,8 @@ later design decision changes them:
 - `/usr/local/etc/notarius/config.yml` for Notarius configuration
 - `/usr/local/etc/scriptorium/config.yml` for Scriptorium configuration
 - `/usr/local/share/narratio/campaigns` for version-controlled campaign data
+- `/usr/local/share/narratio/prompt-library` for version-controlled prompts
+  and schemas
 - `/usr/local/src/<app>` for root-owned application source checkouts
 - `/usr/local/bin/<app>` for root-owned application binaries
 - `/var/lib/narratio` for durable workspace and session state
@@ -266,8 +292,8 @@ later design decision changes them:
 The Narratio role creates and configures the campaign root; the pipeline role
 populates it from the selected campaign source. `/usr/local/share` assumes Git
 is authoritative and operators do not edit campaign content directly on the
-managed host. The exact prompt-library checkout and installed-content paths
-remain to be designed.
+managed host. The prompt-library checkout retains its upstream `prompts/` and
+`schemas/` layout at the fixed root above.
 
 ## Deferred Beyond the MVP
 
@@ -276,6 +302,7 @@ remain to be designed.
 - Installation from prebuilt application release artifacts
 - Deploying or managing WhisperX
 - Versioned Narratio prompt-library releases and pinning
+- Versioned campaign-content releases and default release pinning
 - A role-managed scheduler or persistent Narratio service
 - Cryptographic artifact verification, supply-chain hardening, and protection
   against adversarial source or dependency infrastructure
@@ -290,8 +317,6 @@ The following areas require investigation and decisions before implementation:
 
 - The mechanism used to incorporate the independently developed pipeline role
   into collection releases
-- The prompt-library destination and its integration with Scriptorium
-- The campaign repository's checkout revision and deployment/update policy
 - Secret injection and storage
 - Suite-level operator-selection variables
 - Upgrade, downgrade, and removal behavior