FPF.Reference:16.7.1 - Method, MethodDescription, WorkPlan, and Work remain distinct
Preface node
heading:fpf-reference-16-7-1-method-methoddescription-workplan-and-work-remain-distinct:1674
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
A Method is a reusable way of doing. A MethodDescription is an episteme about one admitted Method. A candidate Method account can be improved, compared, and tested while its candidate status remains explicit. A WorkPlan is about intended Work. To assert a dated Work occurrence, use the full independent A.15.1 admission basis, including its A.13 performer, construction and actual performance, enacted Method, temporal extent and required containing-System relation. Ground its result and any additional relations separately when those claims are needed.
A team that writes a playbook, schedules a trial and publishes the text still needs separate grounds for Method qualification and for actual enactment.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)