A Pairing Manifest That Stops Generated Edits Outside One Module

Description and use

A pairing workflow using a rewrite‑set manifest and a local checker prevents unintended file edits, restricting changes to specified paths and ensuring rollback control.

Problem

Generated patches often touch unrelated files, causing silent failures and rollback complexity in shared modules.

Outcome

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.

Workflow

• 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

Evidence

A generated patch should stay on the laptop until a pairing names one rewrite set and one owner.

Source

The script below is an unexecuted example for review, not a claim that a repository already enforces this gate.

Source

The workflow below is a proposal for the same kind of pairing, labeled so nobody mistakes it for a measured case study.

Source