A bounded refactoring workflow that live-tests the system, runs an independent review, commits checkpoints, and records progress.

Use when

Use this for a deliberate architectural refactor where the destination can be stated in concrete terms and the current system can be tested after each meaningful change.

The loop

Refactor until you are happy with the architecture. After each significant step, live-test the system, run autoreview, and commit. Track progress in /tmp/refactor-{projectname}.md.

Steps

Write down the architectural target, constraints, and current risks before editing code.
Make one significant, reviewable change at a time.
Live-test the affected behavior and run an independent review after each significant step.
Commit each verified checkpoint and update the temporary progress file with decisions, blockers, and the next action.

Verification

The architecture is satisfactory and checks pass. Live-test, autoreview, and commit each significant step.

Why it works

Small verified checkpoints reduce refactor risk and preserve rollback points. The progress file keeps the goal and decisions available across long sessions or handoffs.

Maintain The architecture satisfaction loop?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[![The architecture satisfaction loop on getagentictools](https://getagentictools.com/badge/loops/architecture-satisfaction-loop.svg)](https://getagentictools.com/loops/architecture-satisfaction-loop?ref=badge)