Requests¶

Purpose¶

Owns lightweight export workflow request models used by export systems and panels.

This territory exists to transport export workflow configuration between UI, orchestration, and execution systems without tightly coupling them together.

Owns¶

Export request models
Quick export request payloads
Lightweight export workflow transport models

Does NOT Own¶

Export orchestration
Capture execution
Rendering implementation
Preview lifecycle ownership
Panel UI behaviour

Allowed Dependencies¶

Requests may depend on:

Enums
Lightweight abstractions/contracts
Unity primitives/types

Requests should avoid depending on:

rendering systems
orchestration systems
panel/UI systems

Notes¶

Requests are intentionally lightweight workflow payloads.

They should remain: - transport-focused - side-effect free - explicit

The goal is predictable workflow data flow rather than hidden parameter chains.

Future Candidates¶

Keep request models lightweight.
Avoid embedding workflow logic into request containers.
Prefer explicit workflow configuration over hidden defaults.