In this analysis
Understanding an image, requesting a tool and producing a real visual artifact are separate acceptance boundaries.
The word multimodal can conceal an important asymmetry. A model may interpret a screenshot and produce a text answer without generating an image at all. Sol and Luna’s release made that distinction operationally relevant for applications presenting several AI capabilities through one interface.
The chronology describes an input-output contract
The Responses architecture article, dated September 22, 2025, discussed multimodal workflows. The API changelog records Astra on September 3, 2026 and Sol and Luna on September 22, 2026. For the latter release it specifies text and image inputs with text output. The family announcement supplies the model-positioning context. An input capability is not an output entitlement.
Two requests can mention the same image
Consider a user uploading a shipping label. Asking which order number appears on it is an interpretation task. Asking for a revised label with another layout requires a generated artifact. The second request might involve a drawing tool, a document generator or a separate image model.
A fluent textual description of the revised label does not fulfill that artifact request. An application that displays both outcomes as a completed image task hides the missing operation. The failure is a capability-routing defect even if the interpretation step was correct.
Output inspection needs its own boundary
The application should identify what it expects to receive before selecting a model path. A text answer needs content checks. A generated document needs a real file with the requested fields and layout. A raster image needs an actual image output, not a markdown sentence claiming one exists.
These acceptance objects remain different when one model coordinates them. A coordinator can describe or request another operation without performing it. The event therefore supports a distinction between understanding, planning and artifact production rather than a broad claim that multimodality unifies every step.
A paired fixture reveals false completion
Use the same uploaded label for an extraction request and a redesign request. Preserve the source image and intended output type. Check the extracted order number against the image, then inspect whether the redesign path produced a usable artifact.
If the model requests a supporting tool, retain its returned artifact identifier and verify that the final response resolves to it. If no production path is available, an explicit limitation is a more accurate result than an invented download link. The fixture tests task completion without requiring a claimed generation speed.
What this changes in a product
Capability labels should describe direction as well as modality: what enters and what leaves the system. That information helps routing, testing and user expectations at the same time.
Sol and Luna broadened visual reasoning choices, but the release did not erase output boundaries. Keeping those boundaries explicit prevents an application from converting successful interpretation into an unsupported promise of media creation.