Goal Preserving Pivoting · aryanrogye Use this when debugging feels stuck, circular, or is giving misleading signals — especially when the problem crosses boundaries like permissions, sandboxing, IPC, app extensions, files, networking, async lifecycle, OS APIs, or multiple processes. Instead of repeatedly tweaking the same broken path, keep the end goal fixed and swap the mechanism for something simpler or fundamentally different, testing one assumption at a time to reveal which layer is actually failing. Trigger this whenever you notice yourself making the same fix repeatedly, getting inconsistent results from the same approach, or suspecting the bug is one layer deeper than where you're currently poking at it.
