alexandrenunes-cs

engineering-solution-pivot

Deep-reasoning escalation method, not a default workflow, for engineering problems where the obvious path is exhausted or is heading toward a dead end or an expensive path. It is evidence-driven, escapes blocked or thrashing approaches, and challenges designs, constraints, and assumptions — including transforming a constraint rather than working around it. Use when the same causal hypothesis has failed twice; a workaround is growing more complex than the problem it solves; a constraint, dependency, platform limit, or security control appears to make the goal impossible; a request is framed as "do X using Y" and Y may not be required; an architecture, migration, or design decision carries significant security, reliability, performance, or cost trade-offs; or the user asks for alternative approaches, a devil's-advocate or adversarial review of a technical plan, an engineering pivot, or invokes /engineering-solution-pivot. Not for routine tasks with a clear, working path.