pre-edit-investigation-gate

Prevent blind edits by enforcing a pre-edit investigation gate that validates evidence of affected files and dependencies before modifying architecture, auth, or data components. This ensures thorough inspection of risky changes before proceeding.

Pre-edit investigation in secure development is the process of collecting and validating evidence regarding affected surfaces, known invariants, and expected validations before modifying critical software components.

Enforce evidence collection by requiring manual validation of affected surfaces and known invariants before proceeding with risky edits. This integrates with task traces to monitor pre-edit events for critical files.

Yes, the pre-edit investigation gate works with task trace monitoring by utilizing existing task-trace.jsonl files to track inspection and pre-edit events for high-risk changes.

A pre-edit investigation gate is required for risky changes to architecture, data, auth, dependencies, migrations, workflows, and UI/API behavior to ensure all relevant files are inspected.

Yes, you need to manually validate known invariants and affected surfaces as evidence before proceeding with risky code edits. This manual evidence collection is required by the investigation gate.