The stakeholder demands a feature that breaks the architecture. What are the actions?

If a stakeholder demands a feature that breaks the architecture, it is important to act as follows:

1. Understand the requirements and motivation — find out why this feature is needed and what problems it solves.
2. Assess the consequences — explain how implementation will harm the architecture, lead to technical debt, and complicate support.
3. Offer alternatives — perhaps there are other solutions that meet the needs without compromising the architecture.
4. Document the risks — record potential issues and their impact on the project.
5. Make a joint decision — discuss with the team and stakeholders to reach a compromise or a refactoring plan.

The main thing is not just to refuse, but to conduct a constructive dialogue, demonstrating professionalism and concern for product quality.