gating-work-before-speedlisted

# Gating Work Before Speed ## Core Rule Stating the goal is not enough; constraints must be front-loaded as gates. AI optimizes for "getting the feature built" — not for delivery-path correctness, change-scope control, or declaring its own boundaries. It follows the easiest-to-verify path, and the easiest path silently becomes the delivery path unless a gate stops it. The human's half of AI development is the half AI structurally lacks: boundaries, ownership, and closure. Compressed: **先管边界，再管速度。** ## Five Questions Before Any Work Starts The implementer (AI or human) must answer all five before touching anything: 1. **用什么契约？** — which agreed interface/contract governs this work 2. **用什么数据源？** — which source of truth, and is it real or a stale copy/stub 3. **改哪一层？** — exactly which layer/module/repo will be modified 4. **怎么证明？** — what evidence will demonstrate completion 5. **不能做什么？** — the explicit forbidden list for this task Unanswered questions are open gates. Work does not start through an open gate; parallel work especially — sessions advancing under different unstated assumptions produce synchronized rework, not progress. ## Three Admission Gates | Gate | Rule | |---|---| | Contract | 没有统一接口契约，不允许进入并行实现。 | | Data source | 数据源和主数据没确认（真实源头 vs 快照/缓存/假数据），不允许验收。"测试通过"用的若是假数据，什么也没证明。 | | Invasiveness | 没有完成实现路径侵入性确认，不允许进入正式实现。 | ## Invasiveness Halt The moment an implementation path requires modifying business code, platform shell, or shared component libraries,