Processing¶
Purpose¶
Owns concrete pixel-level style processing implementation.
This territory applies grayscale, hue/saturation, posterization, flipping, and pixelation effects to Texture2D output used by preview and capture workflows.
Owns¶
- Pixel-level style processing
- Texture copying/replacement helpers
- Grayscale processing
- Hue/saturation processing
- Posterization processing
- Flip processing
- Pixelation processing
Does NOT Own¶
- Style state ownership
- Export orchestration
- Capture workflow planning
- Preview lifecycle
- Panel UI
- Rendering pipeline implementation
Allowed Dependencies¶
Processing may depend on:
- Style abstractions/contracts
- Unity texture/color APIs
Processing should avoid depending on:
- preview orchestration systems
- export systems
- panel/UI systems
Notes¶
Processing is implementation territory.
It owns how style effects modify pixels. It does not decide why or when those effects should apply.
Texture ownership and replacement should remain explicit because this territory creates and destroys temporary textures.
Future Candidates¶
- Keep processing implementation isolated and deterministic.
- Avoid adding workflow decisions to pixel processing systems.
- Maintain clear cleanup ownership for generated textures.