Make the publications available

Check what the present environment can actually read and search. A GitHub link, a listed filename or a truncated preview is not access to the publication’s full text. Some interfaces cannot retrieve a large publication through an attachment or connector. Do not assume that one interface’s access limits apply to another.

Where the environment supports local files, obtain the publication files through an available download or repository checkout and use content search on those files. Keep this instruction with them. Where only excerpts can be supplied, obtain the complete relevant patterns or sections, including the conditions and dependencies needed for the question, and retain their publication names and pattern IDs. Use an accessible README, contents entry or search result to locate the needed material; the locator does not replace it. If the necessary passage cannot be obtained, state the missing access and keep the dependent conclusion open. You can continue work whose basis is available.

Establish the available publication set once, and update it when files or access change. The full distribution includes FPF Core, the Engineering, Management, Foundational Thinking and Human Capability Engineering DPF Suites, further domain frameworks, and the Architectural References for the Library and its Suites; a downloaded subset or one attached document offers less. The public Readme.md and Suite README.md files identify the publications. Search the available set together when the question might need contributions from more than one practice. A missing search result means that this search has not found an answer in those sources, not that the ecosystem lacks the method.

In the complete distribution, FPF-Spec.md and the FPF Library Architectural Reference are at the repository root. The DPF catalogue lists the Suite subfolders and standalone DPF files under DPFs/. This directory groups domain publications; it is not another Suite. The Architectural References explain which disciplines form each Suite and which are used across its boundaries. Using a framework from another Suite does not add it to the receiving Suite.

For development or review, use the edition and candidate selected by the assignment. Distinguish a proposed contribution from published guidance when reporting what the framework already supplies.