why-here reviews a change before delivery by asking of each questionable part: why is it here now? It keeps what the finished result still needs and removes what exists only because the work took a particular route.
- Scopes the review to the current diff, user-named files, and anything delivered with this change; review-only unless the user authorizes edits.
- Derives the finished result from the request, acceptance criteria, owning documentation, current contracts, and real consumers; marks a target unproven instead of inferring it from the current implementation.
- Uses the counterfactual only to find candidates: a removal must be supported by current callers, contracts, stored data, and external constraints.
- Classifies each candidate as Keep, Confine, Remove prose, Remove structure, or Unproven, and leaves unproven candidates unchanged.
- Requires explicit authorization before touching a public interface, durable data, wire format, migration history, or a still-used compatibility path.
- Reports the finished state, remaining constraints, and checks actually run, instead of a removal diary.
why-here 在交付前审查一次改动，对每个可疑的部分问同一个问题：它现在为什么还在这里。完成后的结果仍然需要的留下，只因为做的过程走过某条路才存在的删掉。
- 审查范围是当前 diff、用户点名的文件，以及随本次改动一起交付的产物；用户没有明确授权修改时只审查和报告。
- 从请求、验收标准、相关文档、当前契约和真实调用方推导完成后的结果；依据缺失或矛盾时标记为证据不足，不从当前实现反推。
- 反问“从完成后的设计开始还会加入它吗”只用来找候选项，删除必须由当前调用方、契约、已有数据和外部约束支持。
- 每个候选项归入保留、限制在转换边界、删除文字、删除结构或证据不足；证据不足的保持原样。
- 改动公开接口、持久化数据、传输格式、迁移历史和仍在使用的兼容路径前，先取得明确授权。
- 最终回复说明完成后的状态、仍然成立的约束和实际跑过的检查，不生成删除日记。
im0o released this