Repeated quality-improvement loop
Route
route:repeated-quality-improvement-loop
What this page is
This is an FPF route: a curated working path through pattern IDs. It is not a website route or application navigation route.
Methodology
Use the ordered steps as the first path through the framework. Treat optional steps, landing points, route surfaces, and reroutes as controls for scope, ownership, and common wrong turns. Open exact pattern pages only when the work depends on their wording.
- First Honest Burden: "The object has an evaluation and candidate repairs; now we need repeated read, change, re-read, and stop without treating activity as improvement."
A.19.ECS when the evaluation is missing or inadequate; C.19/G.5 when proposal or candidate-pool selection is live; A.10, B.3, A.20, A.21, or A.15 when the loop result is overread as evidence, assurance, decision, gate, or work
Route surfaces
- E.23 Quality Improvement Loop Method
- E.22 Improvement-Oriented Quality-Read Question Framing
- E.21 FPF Pattern-Quality Evaluation CharacteristicSpace
- E.9.DA DRR Decision-Adequacy Evaluation CharacteristicSpace
- E.2.DA FPF Pillar-Adequacy Evaluation CharacteristicSpace
- C.25 Q-Bundle: Authoring "-ilities" as Structured Quality Bundles
Citations
J.4
Last Updated: 2026-05-31 — upstream FPF commit 16cd3138 (github.com/ailev/FPF)