A strategic customer needs a permanent product fork to launch on time. Would you build it, and who should own the consequences?

Instruction: Use an actual extension boundary, delivery constraint and maintenance owner. Commercial commitments require approval; a product fork is not automatically acceptable or automatically wrong.

Context: Tests lifecycle ownership and a defensible architectural recommendation when a customer deadline creates pressure to accept permanent divergence.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

My first choice would be a supported extension or narrower workflow if it meets the customer's essential need...

Upgrade to view official answer

Related Questions