Overview
A specification-to-code mindset encourages people to stop examining the code. When the output is wrong, they edit the specification and run the conversion again. This weakens engineering control because the codebase is the actual system being changed. Its modules, dependencies, tests, and failure modes cannot be delegated to an abstract document.
A destination document is still valuable. It externalizes the shared understanding, gives the implementation planner a stable target, and records negative decisions that define completion. The difference is that it supports engineering judgment rather than replacing it.