prototype-coupling-safely-bounded-by-registry-infrastructure

Status: OUT

Prototype's position at the maximally-coupled extreme of the creational spectrum (triple implementation burden: mandatory Clone, deep copy for independence, separate Initialize) is structurally bounded by the registry meta-mechanism (Prototype Manager providing key-to-instance lookup that decouples clients from Clone complexity) — but only while the deep-copy requirement for structural independence does not defeat the sharing optimizations that make the registry approach practical.

Justifications

Registry infrastructure bounds Prototype's coupling extreme, but deep-copy requirements can undermine registry-based sharing

Depends on (SL): creational-coupling-spectrum-informs-pattern-selection, registry-meta-mechanism-spans-creational-patterns

Unless: prototype-deep-copy-required-for-independence

JSON