Virtual Screens Feature Example

Virtual Screens is a placeholder cross-repository feature playbook. It shows how this product repository should frame a feature before creating repository-specific tasks. It is not a full implementation plan.

flowchart TD
    Feature["Virtual Screens"]
    Product["Product planning"]
    Web["anuvax-cms<br/>authoring and config"]
    Python["anuva-python-server<br/>validation and orchestration"]
    Unity["anuva-unity-video-creator<br/>runtime presentation"]
    Review["Cross-repository verification"]

    Feature --> Product
    Product --> Web
    Product --> Python
    Product --> Unity
    Web --> Review
    Python --> Review
    Unity --> Review

Product Intent

Virtual Screens should allow presentation scenes to include screen content that is authored, configured, validated, rendered, and reviewed as part of the Video Creator workflow.

Placeholder Repository Impacts

Repository	Possible Product Impact
anuvax-cms	Author screen moments, store media references, and compile PresentationConfig fields.
anuva-python-server	Validate render job inputs and pass screen-related configuration to Unity.
anuva-unity-video-creator	Render screen content in scenes with camera and timing behavior.

Planning Notes

• Define user-facing authoring behavior before implementation tasks are created.
• Define PresentationConfig contract changes before downstream work begins.
• Create separate task prompts for Web, Python, and Unity.
• Review completion across all affected repositories before release notes are written.