Export¶
Purpose¶
Owns export orchestration workflows for Snap Studio Pro.
This territory coordinates production export flows including batch export, multi-angle export, spritesheet/GIF assembly routing, export request planning, folder organization, and export lifecycle coordination.
Export orchestrates production workflows.
Capture executes them.
Owns¶
- Export workflow orchestration
- Batch export workflows
- Multi-angle export coordination
- Export request planning
- Export folder organization
- Export assembly routing
- Export lifecycle coordination
- Export progress coordination
- Export-facing preference persistence
Does NOT Own¶
- Low-level rendering implementation
- Capture execution internals
- Preview scene lifecycle ownership
- Panel UI layout ownership
- Render pipeline implementation
- Texture compositing implementation
Allowed Dependencies¶
Export may depend on:
- Capture systems
- Preview systems
- Rendering abstractions
- Infrastructure services/runners
- Directional capture workflows
- Assembly systems
- Shared abstractions/contracts
Export is allowed to coordinate across multiple systems.
Notes¶
Export is intentionally orchestration-heavy territory.
It owns: - how export workflows are coordinated - how export batches are planned - how output assets are assembled - how export jobs progress - how export folder structures are organized
Capture owns: - how images are actually produced
Rendering owns: - low-level pixel/render implementation
Preview owns: - live preview coordination
This separation is one of the core architectural boundaries in Snap Studio Pro.
Large orchestration services are acceptable here when they reflect real export workflows.
Future Candidates¶
- Continue protecting the Export/Capture boundary.
- Avoid moving rendering implementation into Export.
- Maintain explicit workflow stages and predictable export coordination.
- Continue isolating reusable output assembly systems from export orchestration.