Jump to text
On this page
Copy and source
Original source · lines 21–32
Published source confirmed at last check

Source changed 2026-10-15 18:27:28 UTC · snapshot created 2026-10-15 18:29:21 UTC · last check 2026-10-16 06:50:10 UTC

Resolve a portable reference

A portable reference keeps the complete PatternID or SectionRef and enough context to recover the intended publication set and document. Add a document qualifier only when that identity is not already clear from the complete address and the context that travels with it. In this distribution the publication set is FPF Library. Its document catalogue (Library.Reference:11.1) associates 39 declared DocIDs with their full titles and current files. Short navigation and usage publications can be named by their full titles without a DocID. A DocID identifies a whole document; it does not turn its embedded Architectural Reference into a separate framework or identify an edition.

For example, within FPF Library, HCD.12:4.1 locates a section of the Human Capability Development Principles Framework, and Library.Reference:9.1 locates the Library’s explanation of connected development. Those complete addresses already identify their declared documents. Use FPF C.39:4.1 when a Core reference needs a document qualifier. These addresses have different structures; resolve each complete address under its declarations. Retain every suffix and every member or endpoint of a referenced list or range. Name a selected edition separately when its exact published content matters.

A whole-document reference can use its declared DocID or full title within the identified publication set. For an unnumbered heading, give its title and enough document context: Practical entries in HCD distinguishes that heading from the heading of the same name in Core.

First look for the declared document among the files available to you. Match its DocID and title, then search for the exact heading address and read the relevant section with its conditions. A GitHub hyperlink can help open a carrier, but its hostname and path are not required to identify the contribution. If local files are unavailable, search by the publication set, document title or DocID, and full local address through the web or an available search, fpf.tools or MCP interface. Use only the access that the present interface actually provides; this instruction does not assert a special API or that any service indexes the complete Library.

Check that the returned text belongs to the intended document and contains the requested target. Keep the complete local address with any extracted fragment and restore any publication-set, document or edition context that will no longer accompany it. A search hit, similarly named pattern or newer edition is not a substitute for an unresolved target or a requested exact edition. State that limit and continue only work whose needed basis is available.