Refactor with behavioral boundaries

---
name: safe-refactor
description: "Improve structure while preserving observable behavior and compatibility."
license: CC0-1.0
metadata:
  author: "SI Editorial"
  version: "1"
---

# Refactor with behavioral boundaries

## When to use
Improve structure while preserving observable behavior and compatibility.

## Workflow
1. Identify the behavior to preserve and the structural problem to change.
2. Map callers and boundary cases before editing.
3. Make one coherent change, preserving public interfaces unless explicitly approved.
4. Run relevant checks and compare before/after behavior. Report residual risks.

## Boundaries
Use only tools and data authorized for the task. Ask for missing requirements when they affect the result. Report what you verified and what you could not verify.

## Try it
Separate validation from this route without changing its responses.

## Success looks like
A focused change with evidence that existing callers still work.