# Rendering Backend Options

Sprint 1.5 decision: keep the current Python/Pillow/FFmpeg renderer active.

## Current active backend

- `python_motion`
- Python/Pillow writes deterministic preview frames.
- FFmpeg assembles local MP4 previews at explicit renderer boundaries.
- This remains the production path for now.

## Remotion spike candidate

Remotion is noted only as a later spike candidate, not an active migration.

Potential advantages:

- React/CSS-based motion language.
- Better UI-style animations and component reuse.
- Easier complex timeline composition for some motion-graphics patterns.

Risks:

- Adds Node/React stack to a currently Python-centered pipeline.
- More build/deploy complexity.
- More moving parts before the editorial gates, scoring, claims, disclosures, and analytics are stable.

## Decision

No Remotion implementation now. No renderer migration in Sprint 1.5. Revisit only after V2 strategy, review, claim gate, disclosure gate, and analytics loop are stable.