Skip to content

Engine

Purpose

Owns capture execution routing and concrete capture executors.

This territory receives capture requests and routes them to the correct capture implementation, such as static capture or animation capture execution.

Owns

  • Capture engine routing
  • Static capture execution
  • Animation capture execution routing
  • Capture request models
  • Capture output preparation
  • Capture texture cleanup responsibility

Does NOT Own

  • Export workflow planning
  • Batch export orchestration
  • Preview scene lifecycle ownership
  • Rendering pipeline implementation
  • Panel UI
  • File path strategy beyond request execution

Allowed Dependencies

Engine may depend on:

  • Rendering abstractions
  • Infrastructure file/encoding services
  • Styling systems
  • Overlay systems
  • Animation capture execution
  • Background generation/compositing abstractions

Engine should avoid depending on:

  • panel UI systems
  • window lifecycle systems
  • high-level export coordinators

Notes

Capture.Engine is the practical execution layer.

It should answer: - what capture type is being executed? - what texture should be produced? - should background/style/overlay processing apply? - how is the final capture saved?

It should not answer: - how many captures are needed? - what export workflow is running? - which batch mode is active? - what UI triggered the operation?

Those decisions belong to Export or Panels.

Future Candidates

  • Continue keeping capture execution separate from export planning.
  • Maintain explicit cleanup of temporary textures.
  • Avoid expanding CaptureEngine into a general export manager.
  • Keep request models lightweight and execution-focused.