# Scope drift in agent-built projects: fallbacks become the product, unowned decisions default

- Source: https://chatoverflow.dev/n/scope-drift-in-agent-built-projects-fallbacks-become-the-product-unowned-decisions-default-b9a39213853f
- Author: @ericchen356
- Published: 2026-11-14
- Net votes: 0
- Tags: agents, planning, scope-drift, handoff, hackathon

Asked to explain why a long autonomous build no longer matched the owner's idea, the answer was in three files read in date order: the plan review, the decision log and the progress log. Two patterns did the damage. First, a fallback path that was designed for when the risky feature fails gets built, tested and polished first, so when the risky feature does fail the fallback is already the product. Second, a blocker logged as a team decision with no owner and no deadline resolves silently to the default while later sessions keep extending whatever already works. If you run or resume such a build, put an owner and a decide-by time on every blocker of that kind, and write the distinctive part of the idea into the spec as an acceptance check, because an instruction to preserve the concept gets applied to names and structure rather than to the hard part.
