FPF source locators
The complete FPF Markdown is available as a raw file. GitHub’s file page may refuse to render the large document. Open or save the raw Markdown in a text or Markdown reader and search for the following PatternID and heading. FPF links in this publication return to that full file, not to a promised rendered fragment.
| FPF PatternID | Source heading to locate |
|---|---|
| A.2.3 | U.PromiseContent — Promised Outcomes and Acceptance Criteria |
| A.3.1 | U.Method: Reusable Way of Doing with Explicit Applicability |
| A.3.2 | U.MethodDescription: Description Episteme for a Way of Doing |
| A.10.1 | Revalidate Affected Uses When a Relied-on Source Changes |
| A.15.9 | Use or Request a Bounded Result from Another Practice |
| C.11.CRC | Configuration-Relative Contribution Comparison |
| C.11.DUA | Make Advice and Evidence Demands Worth Their Burden |
| C.16 | Measurement & Metrics Characterization (MM‑CHR) |
| C.17 | Characterising Generative Novelty and Value |
| C.18 | Open-Ended Search Archive and Front Stewardship |
| C.19 | Explore-Exploit Live-Pool Governor |
| C.40 | Develop Branching Search from Reusable Material |
| C.40.CD | Develop Problems and Ways of Solving Them Together |
| E.10.DEV | Recovering What Development or Evolution Means in the Current Claim |
| G.11 | Decide Whether and How to Refresh (Telemetry and Decay) |
Use the complete relevant pattern and its conditions, not just the matched title. In particular, A.10.1 supplies bounded changed-source discovery and actual-use qualification; DOCA.8 requires a subject basis before asserting restored qualification, but may finish with a supported limit or compatible reference repair. It does not require a second result record or an unused common summary. A different edition or wording requires comparison of the relied-on contribution when that difference could affect the receiving use.