aboutsummaryrefslogtreecommitdiff
path: root/.ai/workflows/code-quality.org
diff options
context:
space:
mode:
Diffstat (limited to '.ai/workflows/code-quality.org')
-rw-r--r--.ai/workflows/code-quality.org7
1 files changed, 7 insertions, 0 deletions
diff --git a/.ai/workflows/code-quality.org b/.ai/workflows/code-quality.org
index 3ac3e9d..0481166 100644
--- a/.ai/workflows/code-quality.org
+++ b/.ai/workflows/code-quality.org
@@ -9,6 +9,13 @@ One trigger that runs every behavior-preserving quality pass over a scope of
orchestrator — each pass keeps its own discipline and its own confirm gate; this
workflow only sequences them and collects the residue.
+*Behavior-preserving rests on a test net.* The passes below claim to preserve
+behavior, but a refactor on untested code is a guess, not a preservation. Where
+the scope has no tests, bring it under a characterization net first
+(Normal/Boundary/Error per unit, per =testing.md='s "Adding Tests to Existing
+Untested Code") — that net is what turns "behavior-preserving" from an assertion
+into something the green suite actually verifies across each pass.
+
The passes it chains:
1. =/refactor= — structural and logic cleanup on measurable metrics (complexity,