E.4:4.2.3 - Build the larger pattern language
Develop the Suite as a framework under E.4.DPF and E.8. Its entrance explains the composite field, the contribution of each constituent and the important relations between them. A long mantra can help a practitioner retain a connected Method, but neither that phrase nor a Reference substitutes for the Methods it recalls.
Give a whole-level Method its own pattern when it removes a recurring difficulty that the constituent Methods do not independently solve. State its problem frame, problem, forces, construction, limits and cases. The construction may consume results from several DPFs and return questions to them. If a contribution is transdisciplinary, develop it in Core instead of hiding it in a Suite introduction. If the missing work is specific to one subdiscipline, develop it there. If it reveals another field, reopen the field architecture rather than stretching a pattern or an appendix around it.
Expose enough of the language for a reader to select constituent Methods, understand their contributions, combine them where justified and retain their separate assurance obligations. Preserve alternative configurations; a Suite is not a mandatory sequence through every DPF. Use E.11.PFP for the Suite’s framework entrance and constituent frameworks. Use E.11.DSG to develop the Suite’s architectural reference, including useful problem-led entries. It covers the whole’s architecture and can return both constituent and external contributions, labelled by their relation.
An additional explanation of already described Methods belongs in the relevant pattern or architectural reference. A useful new operation or composition needs its own complete E.8 pattern; a mantra or reference entry cannot hide its missing construction.
A teaching course or Guide with a separate learning purpose is a pedagogical companion, while explanations and cases needed to use or adapt the language remain with that language.