Quality-read question framing before review or improvement
Route
route:quality-read-question-framing-before-review-or-improvement
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: "Are we asking for blockers to floor, exceptional improvements, trade-off check, missing questions, or absorption impact?"
C.16/A.17-A.19 when characteristic or scale legality is live; E.10/A.6.P/C.2.P/F.18 when wording or names carry FPF force; A.10, B.3, A.21, or A.15 when a quality result is overread as project evidence, assurance, gate, or work authority
Route surfaces
- E.22 Improvement-Oriented Quality-Read Question Framing
- E.21 FPF Pattern-Quality Evaluation CharacteristicSpace
- E.9.DA DRR Decision-Adequacy Evaluation CharacteristicSpace
- E.19 Pattern Quality Gates: Review and Refresh Profiles
Common wrong reroutes
- E.21 FPF Pattern-Quality Evaluation CharacteristicSpace
- E.9.DA DRR Decision-Adequacy Evaluation CharacteristicSpace
- E.19 Pattern Quality Gates: Review and Refresh Profiles
- 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)