A Pairing Manifest That Stops Generated Edits Outside One Module
说明与用途
使用 rewrite‑set.txt 清单和本地检查器的配对工作流程,防止未预期的文件更改,将更改限制在指定路径内,并确保回滚控制。
问题
Generated patches often touch unrelated files, causing silent failures and rollback complexity in shared modules.
结果
The pairing workflow prevents unintended edits by enforcing a manifest and local checks before any model or server interaction, reducing rollback risk and keeping scope narrow.
工作流
- Write rewrite-set.txt with allowed paths and rollback owner comment
- Run local checker against working tree before model draft
- If checker reports extra path, restore it and shrink prompt
- Request draft only inside allowed paths, then run checker again on diff
- Point dry run at free server only after second checker succeeds
- Record clear rollback command for owner and stop session if unclear
证据
A generated patch should stay on the laptop until a pairing names one rewrite set and one owner.
The script below is an unexecuted example for review, not a claim that a repository already enforces this gate.
The workflow below is a proposal for the same kind of pairing, labeled so nobody mistakes it for a measured case study.
- 记录日期: 2026-10-10T19:40:53.531Z