#DPF Suite and Reference

Preface node heading:dpf-suite-and-reference:70491

#What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

#Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

#Content

Three independently maintained DPF product series already cover one recurring practitioner use. The architecture question is therefore not whether to merge them into another DPF. When one architecture decision takes effect, it constitutes the continuing Suite collection, states its ecosystem use, defines which product series may belong, selects inclusion and removal rules and identity through change, identifies the capable maintaining System and its accepted Suite-maintenance commitment, and chooses source return and exposure. Its E.9 DRR records that answer and the initial inclusion decisions. Each DPF edition still belongs to its own product series under that series rule. The answer separately decides whether a DPF Suite Reference product series is constituted and included, identifies its capable maintaining System and commitment, and states its refresh route. A Reference edition may then give a problem-led cross-DPF answer, but it neither constitutes the Suite nor decides which product series belong. The answer records any proposed cross-DPF result use but makes no dependency or compatibility claim until the edition-level predicates pass. A later author may propose inclusion or removal, but returns that proposal to the Suite decision; one DPF and one Reference edition cannot settle it from inside their own content.

---

Last Updated: 2026-08-30 — upstream FPF commit e400eab3 (github.com/ailev/FPF)