Status: IN
Prototype imposes a significant implementation burden — Clone must be implemented by every subclass (which is difficult when classes weren't designed for it or contain non-copyable objects), separate Initialize methods are needed because Clone's uniform signature cannot accept varying constructor parameters, and deep copy is usually required for independence (with circular references making this particularly tricky) — collectively making the pattern most practical for objects designed for cloning from inception.
Three reinforcing implementation costs explain why Prototype occupies the maximally-coupled position in the creational spectrum
Depends on (SL): prototype-main-liability-clone-implementation, prototype-clone-needs-separate-initialize, prototype-deep-copy-required-for-independence