Abstract pipeline implementation in methodology docs

Author: whystrohm

README.md

@@ -145,11 +145,11 @@ See [`brand-packs/README.md`](brand-packs/README.md) for the full pattern.
 shotkit produces **specs and prompts**, not rendered images or videos. The boundary is deliberate:
 
 - **In scope.** The methodology, the structure, the prompts, the audit trail.
-- **Out of scope.** API integrations to fal.ai or ElevenLabs, the Remotion render pipeline, automated publishing, the 48-hour content cycle.
+- **Out of scope.** API integrations to image generators or voice tools, the video render pipeline, automated publishing.
 
-If you want the version where this is wired into a Remotion pipeline with automated publishing across multiple brands: [whystrohm.com](https://whystrohm.com). The methodology is open. The operator is paid.
+If you want the version where this is wired into a video render pipeline with automated publishing across multiple brands: [whystrohm.com](https://whystrohm.com). The methodology is open. The operator is paid.
 
-See [`docs/connecting-to-generators.md`](docs/connecting-to-generators.md) for how teams typically wire it up themselves, and [`docs/remotion-bridge.md`](docs/remotion-bridge.md) for how `shots.json` maps to Remotion props.
+See [`docs/connecting-to-generators.md`](docs/connecting-to-generators.md) for how teams typically wire it up themselves, and [`docs/connecting-to-video-pipelines.md`](docs/connecting-to-video-pipelines.md) for how `shots.json` maps to programmatic video frameworks.
 
 ---
 
@@ -208,7 +208,7 @@ Apache 2.0. See [LICENSE](LICENSE).
 
 [Yuri Strohm](https://whystrohm.com). Motion Design and Narrative Visualization Specialist, founder of WhyStrohm. A decade of defense-adjacent design work informs how I build content systems: deterministic, auditable, no surprises.
 
-If you want the version where this is wired into a Remotion pipeline with automated publishing: [whystrohm.com](https://whystrohm.com).
+If you want the version where this is wired into a programmatic video pipeline with automated publishing: [whystrohm.com](https://whystrohm.com).
 
 - GitHub: [@whystrohm](https://github.com/whystrohm)
 - Web: [whystrohm.com](https://whystrohm.com)

brand-packs/whystrohm.md

@@ -85,7 +85,7 @@ For kinetic typography content (the Content Spiral pattern): pacing accelerates
 - Site: https://whystrohm.com
 - Brand voice extractor: https://github.com/whystrohm/media-tsunami
 - Past hero films: see `/results` page
-- Content Spiral pattern: documented in WhyStrohm Remotion production bible v3 (internal)
+- Content Spiral pattern: documented in WhyStrohm production bible v3 (internal)
 
 ---
 

docs/audit-trail-pattern.md

@@ -42,7 +42,7 @@ Reading this answers "what does the pipeline need to act on." It's the source of
 - `visual-prompt-forge` consumes it to produce per-generator prompts
 - `storyboard-html-preview` consumes it to render the preview
 - `visual-asset-critic` consumes the relevant shot to critique a generated image
-- A custom Remotion bridge can consume it to render the final video
+- A custom video-pipeline bridge can consume it to render the final video
 
 When the JSON is the source of truth, regenerating any artifact is one command. When the source of truth is "the AI's response," nothing is reproducible.
 

docs/brand-lock-anatomy.md

@@ -70,7 +70,7 @@ The grade is what makes generated images sit next to brand photography. Without
 
 How motion behaves. Camera moves, cut style, text animation, transition vocabulary, pacing rules.
 
-This field flows into the shot-grammar reference (it constrains what `motion` values are allowed per shot) and the Remotion bridge (it parameterizes spring physics, transition lengths, easing curves). Without it, every shot defaults to the global average. With it, shots earn their motion choice.
+This field flows into the shot-grammar reference (it constrains what `motion` values are allowed per shot) and the video-pipeline bridge (it parameterizes spring physics, transition lengths, easing curves). Without it, every shot defaults to the global average. With it, shots earn their motion choice.
 
 ### Voice rules
 

docs/connecting-to-generators.md

@@ -119,15 +119,15 @@ The skill pack writes per-shot VO content into `shots.json`'s `vo` field. It doe
 - **Murf, Resemble, Cartesia**, alternative AI VO providers, same pattern
 - **Human voice talent**, hand them `storyboard.md` (or a derived script doc), receive clean recordings keyed by shot_id
 
-Music and sound design are out of scope for this pack. Most teams handle these in their editorial tool (After Effects, Premiere, Resolve, CapCut) or in a Remotion composition (see [`remotion-bridge.md`](./remotion-bridge.md)).
+Music and sound design are out of scope for this pack. Most teams handle these in their editorial tool (After Effects, Premiere, Resolve, CapCut) or in a programmatic video composition (see [`connecting-to-video-pipelines.md`](./connecting-to-video-pipelines.md)).
 
 ## How to wire up final assembly
 
 Three common paths:
 
 **1. Manual editorial.** Drop generated images, VO files, and text overlays into After Effects, Premiere, or Resolve. Cut to the timing in `storyboard.md`. Slow but flexible.
 
-**2. Remotion programmatic.** Build a React composition that reads `shots.json`, renders each shot from generated images, animates text overlays from `text-overlays.json`, and outputs MP4. See [`remotion-bridge.md`](./remotion-bridge.md). Fast, version-controlled, scales to many brands. This is what WhyStrohm runs commercially.
+**2. Programmatic video framework.** Build a composition (Remotion, Motion Canvas, or similar React-based renderer) that reads `shots.json`, renders each shot from generated images, animates text overlays from `text-overlays.json`, and outputs MP4. See [`connecting-to-video-pipelines.md`](./connecting-to-video-pipelines.md). Fast, version-controlled, scales to many brands. This is what WhyStrohm runs commercially.
 
 **3. CapCut, Descript, hybrid.** For social-first content where speed matters more than precision. Hand off `storyboard.md` to an editor working in a fast tool.
 
@@ -137,7 +137,7 @@ Three reasons this isn't just clever positioning:
 
 **Methodology genuinely is reusable across teams.** A serious operator running their own brands benefits from the brand-lock, audit trail, and shot-grammar discipline regardless of which pipeline they wire up. Open-sourcing the methodology grows the category.
 
-**Pipelines genuinely are operational work.** Wiring fal.ai, ElevenLabs, Remotion, and automated publishing into a 48-hour content cycle across multiple active brands is not "code I can publish." It's a continuously-operated system with infrastructure, monitoring, brand-specific configs, and a person on call. That's a service.
+**Pipelines genuinely are operational work.** Wiring image generators, voice tools, a programmatic video framework, and automated publishing into a fast content cycle across multiple active brands is not "code I can publish." It's a continuously-operated system with infrastructure, monitoring, brand-specific configs, and a person on call. That's a service.
 
 **The two layers serve different audiences.** The methodology serves operators who want to learn or run their own systems. The pipeline serves brands who want the output without operating it themselves. Both are real markets. They don't overlap.
 
@@ -151,7 +151,7 @@ Signs that managed infrastructure starts to make sense:
 - Your output cadence is slower than 48 hours and you want it faster
 - You're spending more time on pipeline maintenance than creative work
 - Generator API breaking changes cost you a day each time
-- You're rebuilding the same Remotion components for every new client
+- You're rebuilding the same render-pipeline components for every new client
 
 These aren't hypothetical. They're the daily friction of self-running content infrastructure at scale. Most teams hit them around the third active brand.
 

docs/why-this-exists.md

@@ -54,7 +54,7 @@ The gap isn't a better dashboard. The gap is the whole *file-native, generator-a
 
 - **Not a video renderer.** The pack stops at prompts and specs. Image generation is the user's choice (Midjourney, Flux, etc.). Video assembly is the user's choice (After Effects, Remotion, CapCut, Premiere).
 - **Not a SaaS replacement for collaborative review.** If your team needs synchronous editing of a panel grid in a browser, Boords is good. This is for teams that prioritize file portability over interface polish.
-- **Not Remotion.** WhyStrohm's commercial pipeline uses Remotion to render the final video from the same `shots.json`. The bridge is documented. The implementation is internal, you can build your own from the pointer doc.
+- **Not a specific render pipeline.** WhyStrohm's commercial pipeline renders the final video from the same `shots.json` using a programmatic React-based video framework. The bridge is documented framework-neutrally. The implementation is internal, you can build your own from the pointer doc.
 
 ## Who should use this