fix

A guardrail-driven protocol enforces validation signals before completing code fixes. You run a deterministic three-pass workflow—Safety, Surface, Audit—prioritizing correctness, compatibility, then performance, while generating pass traces and proof hooks for each finding.

A guardrail-driven protocol validates code changes by capturing invariant_before and invariant_after states, collecting counterexamples, and requiring proof results. It triages issues by severity like security, crash, or logic, and outlines the smallest valid fix before execution.

Triage code issues by categorizing severity into security, crash, and logic buckets. You then outline the smallest valid fix for each finding, capturing invariant states and counterexamples to ensure the patch maintains correctness before execution.

Invariant tracking verifies code reproductions by defining invariant_before and invariant_after states. You collect counterexamples for each finding and generate proof results, ensuring the patch maintains correctness across footguns and incidental complexity.

Auditing code changes for incidental complexity and footguns is best handled through a three-pass workflow. The Audit pass follows Safety and Surface passes, evaluating performance while producing pass traces and proof hooks for each identified finding.

A local validation signal is required to complete a guarded code fix. The protocol enforces this validation signal before delivering any changes, ensuring the patch passes the Safety, Surface, and Audit workflow successfully.