@@ -80,13 +80,25 @@ checked for that operation or failure class and the sensitive-workflow state out
8080hold. Then make the direct change in the current behavior owner. Do not add speculative abstractions,
8181configuration, compatibility, migration, or fallback behavior.
8282
83+ Optimize the complete source-and-test change for deletion and consolidation. Compare a direct edit,
84+ reuse of an existing owner, and a refactor of current related code. Prefer a neutral or negative
85+ total line delta. Add a helper, abstraction, configuration surface, registry, fallback, or
86+ compatibility path only when current consumers adopt it in this change and the complete result
87+ removes more owners, concepts, branches, or lines than it adds. Possible future reuse is not enough.
88+ When a current correctness, security, or accepted-scope contract requires growth, keep the design
89+ direct and record why deletion or reuse cannot satisfy it.
90+
8391Add focused evidence as applicable:
8492
8593- positive behavior that must succeed;
8694- negative or denied behavior that must fail;
8795- error, interruption, recovery, or cleanup behavior;
8896- boundary values, ambiguous state, and alternate entry paths.
8997
98+ Preserve semantic regression coverage, not every existing fixture or assertion block. Extend or
99+ table-drive current coverage when that keeps one setup and one behavior owner. Do not create a
100+ one-use test helper, parallel matrix, or second test file merely to shorten an individual test.
101+
90102State why an evidence category does not apply when omission could hide risk. Use runtime or end-to-end
91103evidence only when the real process, filesystem, network, container, hardware, workflow, or service
92104boundary owns the behavior. Run focused tests after the final behavior-affecting edit and record the
@@ -103,6 +115,11 @@ Consideration and all nine Security Rubric categories to the completed behavior.
103115security control and focused negative evidence that proves forbidden behavior remains denied. If no
104116security control changed, state why and cite the reviewed trust boundaries.
105117
118+ Record the reduction case for the completed design: the current code, owners, branches, parameters,
119+ fixtures, or files deleted or consolidated and the total source-and-test line direction. If the
120+ change grew, identify the current contract that requires that growth. Remove review-driven machinery
121+ when a direct solution is smaller; do not add another layer to compensate for an avoidable layer.
122+
106123Confirm that allowed, denied, error, and boundary behavior remains coherent across failure, retry,
107124cleanup, cached, resumed, and compatibility paths that apply.
108125Re-check the recorded operation and failure class, sibling paths, and sensitive-workflow state
@@ -121,6 +138,7 @@ Use this structure:
121138- Accepted scope authority:
122139- Delivered capability:
123140- Changed behavior:
141+ - Simplification result: <deleted or consolidated structure, total line direction, and required-growth justification when applicable>
124142- Deferred scope:
125143
126144## Changed files
0 commit comments