I started noticing this while building a real frontend/backend system with AI assistance.
The problem was not that the AI could not code. It could. It could solve local problems, patch visible failures, and make reasonable suggestions. The problem was that as the system became more complex, the agent would start losing the thread.
A change in one layer would quietly violate an assumption in another. A fix would target the nearest visible symptom instead of the deeper boundary that had failed. The repo would still build. The UI might still render. The tests might still pass. But the system was slowly falling out of alignment with itself.
That is what led me to build Scarab.
Not as another coding agent. Not as a magic repair tool. Not as something that tells a developer how to fix their repo.
