Procedural Mathematical Motion and Algorithmic Shading Blueprint

Role: Lead Technical Director for Procedural Motion & Mathematical Shading

Context

• Simulation Input Geometry / Field: {{simulation_geometry_source}}
• Governing Mathematical Equations: {{procedural_motion_equations}}
• Target Output Resolution: {{target_video_resolution}}
• Target Rendering & Shading Stack: {{render_pipeline_stack}}
• Scientific Color Transfer Function: {{color_transfer_function}}
• Temporal Coherence Threshold: {{temporal_coherence_threshold}}

Task

Engineer a procedural motion architecture and shader implementation report detailing how to convert raw mathematical equations into procedural, artifact-free, temporal animations for scientific video production.

Method

1. Translate {{procedural_motion_equations}} into vector fields, differential flow maps, and discrete particle simulation solvers.
2. Formulate vertex and fragment shader logic for {{render_pipeline_stack}} to render real-time mathematical surfaces from {{simulation_geometry_source}}.
3. Establish sub-stepping, temporal integration (Runge-Kutta 4th order / Verlet), and velocity advection schemes to guarantee numerical stability.
4. Define optical and chromatic transfer mapping using {{color_transfer_function}} to represent density, velocity, and vorticity without optical clipping.
5. Design custom temporal filtering and motion-blur algorithms to satisfy {{temporal_coherence_threshold}} under sudden phase shifts.
6. Specify dynamic Level of Detail (LOD) and camera frustum culling strategies optimized for {{target_video_resolution}}.
7. Detail fallback strategies for high-frequency noise handling, ray-marching boundary artifacts, and numerical underflow/overflow.
8. Produce pseudocode snippets for critical shader passes and procedural node networks.

Constraints

• Procedural motion MUST be strictly driven by {{procedural_motion_equations}} rather than manual keyframing.
• Shading logic MUST ensure zero temporal flickering or frame-to-frame popping at {{target_video_resolution}}.
• Color spaces must be linear floating-point (ACEScg or Rec.2100) throughout the pipeline before the display transform.
• All code blocks must be provided in clean GLSL/HLSL/VEX pseudo-implementations.
• Memory footprints must stay within standard single-GPU VRAM thresholds during batch simulation.

Output format

Deliver an architectural engineering report containing the following numbered sections:

1. Mathematical Formulation & Differential Field Mapping
2. Temporal Integration & Solver Architecture (including Step Equations)
3. Shader Implementation & Chromatic Mapping Architecture (with GLSL/HLSL/VEX Pseudocode)
4. Anti-Aliasing, Temporal Filtering & Motion Blur Protocols
5. Pipeline Execution Graph & Computational Budget (Targeting {{render_pipeline_stack}}) Length limit: 1300 - 1900 words.

Self-review

• Are the shader algorithms numerically stable across the entire domain of {{procedural_motion_equations}}?
• Does the temporal filtering protocol actively prevent aliasing at high-frequency phase changes?
• Is the mathematical formulation directly actionable by a graphics programmer or technical motion designer?