Library.Reference:12 - The Library and its wider ecosystem

FPF Library is the project’s publication collection. The wider FPF ecosystem also includes other authors’ domain and local frameworks, teaching materials, tools, services and the people and organizations that use and maintain them. A common conceptual dependency does not put all of these products inside the Library or give them one publication or maintenance responsibility.

This distinction lets the public Methods remain complete without making every useful learning arrangement part of the Library. A pedagogical companion can sequence practice, give feedback or adapt material for an audience. Tooling can retrieve a passage, compute a result or perform a declared check. Those contributions need their own capabilities and evidence; the fact that they cite FPF does not establish them. The Library’s Reference explains its architecture and connected language, while learning programmes and operational tools retain their own purposes.

Public architectural reasons belong where they help readers understand and adapt the language: why a boundary exists, which serious alternative it excludes, what a dependency supplies and which condition would reopen the choice. Dated authoring decisions, review correspondence and release records serve other readers. FPF E.11.PFP:4.4 distinguishes those functions without hiding the useful rationale in internal records.

The resulting architecture offers common meanings and reusable general Methods, specialized constructive knowledge and explicit ways to connect them. It also leaves meaningful limits visible: field coverage can be incomplete; source grounds can be disputed or dated; a necessary supplier, capability or authority can be absent. A sufficient answer can be used directly. An unresolved contribution remains a particular work question, rather than being supplied by another label, file or larger diagram.

Original content is published under the terms stated in LICENSE and LICENSING.md (Licensing FPF and its DPF publications). For a specific Method or architectural claim, cite the supplying publication, its edition and PatternID or section address. Cite this account as FPF Library Architectural Reference, using the date at its entry and a Library.Reference section when needed.