Profiles¶
Purpose¶
Owns descriptive metadata and profile definitions for curated studio look-and-feel presets.
This territory stores declarative profile data (descriptions, per-pipeline lighting rigs) without owning preset application or rendering behaviour.
Owns¶
- The LookAndFeelProfile enum
- Preset descriptions
- Look-and-feel profile metadata
- Per-pipeline lighting rig definitions (StudioProfileLightingCatalog)
- Per-pipeline post-processing definitions (StudioProfilePostFxCatalog)
- Human-readable preset explanation helpers
Does NOT Own¶
- Preset application
- Rendering implementation
- Preview orchestration
- Export workflows
- Panel UI
Allowed Dependencies¶
Profiles may depend on:
- Lightweight enums/models
Profiles should avoid depending on:
- rendering systems
- preview systems
- export systems
- panel/UI systems
Notes¶
Profiles are intentionally lightweight declarative systems.
They exist to describe presets (what a profile looks like), not execute them. Application mechanics live in the sibling Appliers territory.
Future Candidates¶
- Keep profile metadata lightweight and descriptive.
- Avoid embedding workflow behaviour into profile systems.