Requests¶
Purpose¶
Owns lightweight request models used to describe animation export and animation capture workflows.
This territory exists to transport animation workflow configuration between panels, controllers, capture systems, and export orchestration systems without coupling those systems directly together.
Owns¶
- Animation export request models
- Animation capture request models
- Directional export request models
- Multi-clip export request models
- Lightweight animation workflow payloads
- Animation export parameter containers
Does NOT Own¶
- Animation export orchestration
- Playback state
- Rendering implementation
- Validation orchestration
- Panel UI
- Preview lifecycle ownership
Allowed Dependencies¶
Requests may depend on:
- Models
- Enums
- Lightweight abstractions/contracts
- Unity primitives/types
Requests should avoid depending on:
- rendering implementation systems
- export orchestration systems
- playback systems
- panel/UI systems
Notes¶
This folder exists to centralize animation workflow payload models and reduce direct coupling between: - panels - controllers - capture systems - export systems
Request models should remain: - lightweight - transport-focused - predictable - side-effect free
Requests are intentionally dumb data containers.
They should not absorb: - workflow execution - validation orchestration - rendering logic - editor behaviour
The goal is explicit workflow data flow rather than hidden parameter chains.
Future Candidates¶
- Continue keeping request models lightweight and transport-focused.
- Avoid embedding workflow logic into request containers.
- Prefer immutable-style construction patterns where practical.
- Maintain clear separation between workflow configuration and workflow execution.