The image workspace is planned around iteration: keep prompts, outputs, and useful variations together while the selected model remains replaceable.
Visible model choice
The selected model and its requirements remain part of the workflow instead of disappearing behind a generic generation button.
Project continuity
Outputs are intended to stay connected to the project, source material, and settings that produced them.
Independent installation
Image support can be installed without requiring voice or video modules, keeping the local footprint aligned with the work.
Move through visual directions without losing provenance.
Image work becomes more useful when every variation remembers the source, model, prompt, and project decision behind it.
Set the direction
Start from a prompt or local reference and choose the installed model that fits the brief.
Branch deliberately
Create variations while keeping their model, settings, and parent result visible.
Return to the project
Keep selected outputs beside the source material and decisions that made them useful.
A visual workspace built around iteration.
A selected result can lead to a remix, edit, or upscale without detaching the new output from the project history.
Image workspaceProject saved locally
Model choice stays visible before and after generation.
The image adapter should make the exact artifact, local runtime, storage needs, hardware fit, and publisher terms inspectable.
An image can become a frame, a reference, or a complete result.
Keep the visual direction inside the project, then add narration or motion only when the work calls for it.
Return to the product overviewImage questions, with the boundaries kept visible.
These answers describe the intended capability workflow while keeping pre-release status, adapter requirements, and third-party terms explicit.