Understand, check or extend a contribution

README pages help you choose; full patterns teach the methods and state their conditions. Read the exact explanation when a recommendation matters. A maintained account of useful approaches can include competing schools, failures and limits; neither the newest standard nor one successful example establishes universal applicability.

For a precise reference, retain the complete PatternID or section address and enough context to identify the publication. Using FPF Library: resolve a portable reference explains how this works across files, search and MCP. You need not learn document codes before choosing what to read.

For an issue or proposed improvement, identify the publication and passage, the working situation, what failed or remains unavailable, and the change you propose. Use the relevant Architectural Reference to understand the current design. The broader FPF ecosystem can include independently authored DPFs, local frameworks (LPFs), guides, tools and services; this repository publishes FPF Library.