Lifecycle Diagram is conflating two levels of states, leading to inconsistencies

The issue with our current application lifecycle diagram (and state machine): it conflates two concepts behind the notion of "application lifecycle":
(1) the general notion of application covering a broad lifecycle from upload to removal,
(2) the narrower notion of run-time with more dynamic states.

That leads to the following inconsistencies:

• Because the same assemblyTemplate can be used to create several Assemblies (as expected for some apps when used in a SaaS context), each one of these assemblies can find itself in a different state (suspended, running...) What state is the application in now?
• just because you delete one instance among several does not bring you back to "deployed".
• a state diagram like ours generally assume that you can find yourself in only one state at a time. E.g. if you go from "deployed" to "Instantiated" then you are no longer "deployed". However, again after an instantiation the assemblyTemplate still exists and is available for new instantiations. That means that you can still do an "instantiate" operation when in the "Instantiated" state. That reflexive transition is missing in our diagram, yet would sound weird... (why would you "instantiate" again if in the "instantiated" state?).
• Also, can you still customize your assemblyTemplate between two instantiations? I'd assume so since we don't try hard to maintain 100% consistency between an Assembly and its assemblyTemplate (can modify the Assembly too).