An OCI instance launch names a compartment, an Availability Domain, a shape and a source image or boot-volume path. Its VNIC configuration also needs the intended subnet and address behavior. Read those references as separate parts of the request rather than treating a familiar display name as a complete machine identity.
The fictional render tasks save one Flex allocation and a private-address intent. The image and Availability Domain labels are original training references. The browser doesn't retrieve an image, allocate capacity or boot a guest. A real launch returns an actual OCI identifier and still needs guest, network, identity and application checks. The assigned CPU and memory values are exercise requirements, not performance or pricing advice.
Review location, shape, source and VNIC intent separately.