Library.Reference:11 - Publications, access and changes of boundary

The public arrangement gives Core its full home in FPF-Spec.md. The DPFs catalogue (Domain Principle Frameworks) locates four Suite folders and ten standalone DPFs. Engineering has four direct constituent descriptions, Management twelve, Foundational Thinking five and Human Capability Engineering two: together with the ten standalone languages, these are thirty-three distinct DPF descriptions. OCE has its full home in Management and MNT in Engineering; neither is directly included in both Suites. Each Suite has its own entry and Architectural Reference and identifies every full description it includes. This root Reference carries the Library-wide explanation. Each complete supplying text has an identifiable public home; this arrangement is a publication view of the richer relations described above.

For connected use, the receiving arrangement needs the full relevant texts, including external suppliers. A Suite directory is not necessarily a self-contained distribution: its constituent descriptions can rely on Core, specialized Suites and outside suppliers. A link names a destination; usable access requires that the reader or assisting agent can obtain its relevant explanation. Using FPF (Using FPF and its DPF Suites) supplies the ordinary search and reading method. An unavailable source narrows the supported answer until the required contribution can be recovered.

The README provides a short entry. The whole-language account explains the framework’s subject, construction, relations and alternatives. That account can be embedded in the same publication as its patterns or carried separately; its explanatory responsibility is the same. Each publication’s table of contents locates its whole-language account. Full pattern bodies supply separately selectable Methods. A reader may enter at any of these levels when the needed conditions remain recoverable.

Current use and a reproducible comparison also have different needs. An ordinary application needs an adequate current source and its use conditions. A comparison between editions needs the identified sources whose changes could affect the conclusion. Publication date, a stable filename and a successful retrieval are not substitutes for those content conditions.

When a framework boundary changes, preserve the complete useful constructions and return to their actual supplying bodies. Distinguish a corrected description of the field from a change to the field itself, and both from a layout or access change. FPF E.4.PFIP governs preservation across reconstructed publications; FPF E.4.PFR handles relied-on edition relations. A reference to a successor title is insufficient if the operation, conditions or receiving use have disappeared.

The affected answer is reopened where its premise changed. A revised mathematical assumption can change a comparison while leaving the authority arrangement intact; an unavailable provider can change realization without defeating retained knowledge. FPF C.39.MC develops methodological continuation from changed conditions, and FPF G.11 supplies the source-currentness question when reliance requires it.

Library.Reference:11.1 - Document identities and current carriers

The following catalogue records the DocID declared by each complete framework or standalone Architectural Reference in FPF Library, its full document title and its current carrier. The title and DocID identify the document in this publication set; the carrier is where this distribution makes it available. DocIDs do not name editions, embedded units or discipline membership. Short navigation and usage publications retain their full titles instead of receiving additional DocIDs.

Refer to a document or contribution in ordinary prose, adding only the context needed to distinguish it. Within FPF Library, HCD.12:4.1 and Library.Reference:9.1 already identify their declared documents as well as their sections. Keep each complete address; add a DocID or full document title when the document would otherwise be unclear. A whole-document reference names the document. A reference to an unnumbered unit includes that unit’s title and enough document context. Name a selected edition separately when its exact content matters. Using FPF and its DPF Suites explains resolution through the access available to the reader.

A catalogue entry helps find a text; it does not establish that a search service has indexed it or that a requested excerpt is complete. If a carrier changes, retain the document declaration and local addresses and update the carrier link. If a title or code becomes ambiguous, use the full document title and publication set until an explicit declaration or maintained reader return resolves the ambiguity.