Preface

Method Engineering begins when a Method’s identity, architecture, selection, description, support, trial, change, or continuation blocks a decision. A domain project merely using a Method remains in its owning domain. The Method becomes the Method Engineering subject only when a decision about that Method or its relations is needed.

This edition fixes its transdisciplinary dependency in FPF dependency and compatibility. The depended-on FPF patterns retain authority over common identities, relations, evidence, structures, Work, comparison, publication, currentness, and cultural claims; this framework retains only Method Engineering moves that change specialist action. Domain Methods, evidence, quantities, legal and safety authority, and consequences remain with the practice that owns them. The patterns return results to engineering, management, learning, music and dance, administration, finance, or another receiving practice without taking over that practice’s decision.

ME.Preface:1 - Method, MethodDescription, WorkPlan, and Work remain distinct

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. Admit an occurrence as Work only after establishing when it happened, who performed it, which admitted Methods they enacted, which Systems and relations it relied on, and its conditions and results.

These distinctions prevent a familiar failure: a team writes a complete playbook, schedules a trial, publishes it in a repository, and then reports that the Method exists and was enacted. Each claim needs its own basis. Tools, prompts, repositories, providers, capability, permission, authority, descriptions, support structures, and results likewise keep their own identities.

ME.Preface:2 - Several structures and several views can coexist

A Method decision may depend on a Method composition structure, a Method unfolding, simultaneous Work, an allocation structure, a subject-and-support arrangement, a description structure, or cultural relations. These structures need not be isomorphic. Name the structure and relation that changes the decision. Do not call every connected arrangement a graph: a mathematical graph is one possible lens only after its nodes, edges, semantics, and use are selected.

Project, process, and case views can expose different claims about the same Work. A project viewpoint may expose dates, allocations, authorities, and decision slots. A process viewpoint may expose recurring input/result and coordination correspondences. A case viewpoint may expose the changing evidence, exception, and next decision. The views do not create three Work occurrences, identify three Methods, or make a WorkPlan into performed Work.

ME.Preface:3 - Reader route and result dependencies do not prescribe Work order

The publication begins with focus and recovery because later decisions need a truthful subject. It then moves through individual qualification and architecture, description and support, and trial and change. This order helps a reader find prerequisites. It is not a lifecycle. Repertoire recovery, description, support repair, trial planning, and source refresh can overlap; a known support or evidence defect can be repaired without traversing every earlier pattern.

Use the smallest entry whose result can change the decision. Follow a dependency only when the receiving result actually consumes it. Stop early when an individual qualification, non-Method return, exact gap, or bounded repair already resolves the working difficulty.

Constituent actions in ongoing work. During a trial of a proposed review Method, asking a participant to explain a unit conversion can constitute part of testing that Method, while the trial constitutes part of developing the team’s way of reviewing. If the trial asks about unaided recognition, supplying the conversion during the attempt changes what the trial can establish. The facilitator needs both the subject knowledge and the ability to elicit performance without supplying the answer. ME.6’s worked case develops this connection; FPF B.1.5.EW recovers it and B.1.5.RS helps compare a substitute constituent. Preparing the trial remains earlier work, not an activity presumed to continue throughout it.

Learning to recover and change a way of working. If you know the work and want to learn how to explain and change its method, use the Reference’s practice with records, first attempts and explained answers. You can save an attempt, compare it with the discussion and correct it yourself. Individual feedback requires a qualified helper and agreed time; the text supplies material for self-checking.

ME.Preface:4 - Status, evidence, and assurance decisions are preserved

Identification, qualification, selection, trial, and effectiveness are different claims. A candidate account does not become a Method because it is coherent, selected for trial, represented well, supported by a tool, or used in Work. A successful occurrence establishes only the observations and results supported by that occurrence.

ME.12 checks coherence among the claims on which a use relies. ME.13 checks bounded fit or transfer. ME.14 judges practical worth against current alternatives. The results can disagree. A Method can be coherent yet poorly fit, fit one situation yet fail transfer, or produce a useful result whose burden makes another alternative preferable.

ME.Preface:5 - What this publication foregrounds and leaves outside

The framework foregrounds choosing and recovering the Method Engineering subject; qualifying candidates and comparing architectures; authoring and comparing descriptions and configuring enactment support; obtaining actual trial evidence and making separate judgments; maintaining variants, introducing Methods into practice and changing cultural continuation; and producing and using connected pattern-language knowledge. The last family is the PLUS-ME profile, not a restriction of the general framework.

It does not contain domain Methods, operating procedures, curricula, legal or safety decisions, software tools, repository designs, statistical identification procedures, or complete organizational-change programmes. Use their direct Methods and authorities. Open a neighbouring DPF only when its specialist result is needed; the Method Engineering framework does not assume that a sibling edition is available merely because its discipline is named.

ME.Preface:6 - Why these Method Engineering questions stay separate

A practitioner often receives a proposed Method as a package: a procedure, a diagram, a tool, a training course and a success story. The costly failure is to change the whole package without knowing which contribution is missing. Method Engineering separates the questions because their useful results and grounds differ. A truthful description may still describe an unsuitable Method; a suitable Method may have poor support; a well-supported trial may still leave practical worth unresolved.

The gain is not a complete framework traversal. It is an appropriately bounded answer that the owning practice can use: a qualified candidate, an architecture alternative, usable description content, a support correction, trial evidence or a separate change decision. The EC-417 application illustrates how these questions connect without creating a Method from a project label. Direct domain work remains outside until a Method-related question actually blocks it.

This separation is also a protection against familiar biases. Source prestige does not admit a Method, a familiar package does not define its parts, and a successful demonstration does not settle fit, causal contribution or worth. Check the subject, receiving use, relied-on conditions and first useful result before accepting a more ambitious account. If a known direct answer already settles the difficulty, stop there.

The cost is maintaining several answers and their dependencies instead of one undifferentiated success claim. Keep them separate only where a difference changes selection, action or reconsideration. ME.1 supplies the smallest subject; ME.5–ME.7 supply qualification and architecture; ME.8–ME.10 supply description and support; ME.11–ME.17 separate evidence, judgments and maintenance. ME.19 can explain why a professional architecture differentiated without treating that history as a justification of its present worth.

Mathematical modeling can contribute both to comparison and to construction. ME.6.MC asks which consequences follow from proposed arrangements: does regrouping preserve the answer, can shared resources meet a deadline, or can an intervening operation invalidate a result? ME.25 uses a mathematical transformation to construct a changed way of working, then returns its preserved properties and changed demands to the practical comparison. A different notation for the same way of working remains a description change.

The mathematical operations are developed in Mathematical Thinking, especially MATH.17 and MATH.18. Computational Thinking, including CMP.14, supplies constructions for interactions among computations. FPF C.29 connects a derived consequence to the work it describes. These contributions let Method Engineering reuse mathematical behavior while preserving the question about the actual method, its performers and conditions.

ME.Preface:7 - PLUS-ME — Pattern-Language Unfolding Situational Method Engineering

PLUS-ME is a profile of the broader, representation-neutral Method Engineering framework. Use it when recurring Method Engineering questions benefit from connected pattern-language knowledge, or when that knowledge must be produced and maintained from unlike sources. It is not a requirement to describe every Method as patterns. ME.22’s content/representation comparison is a general Method Engineering contribution and can be used outside this profile.

ME.Preface:7.1 - Situation, problem and first gain

A Method engineer has a handbook, current research, an existing pattern library and a returned account of local practice. They partly agree, but neither chapter boundaries nor a ready-made process tells the engineer which reusable actions, conditions and unresolved claims should survive. Later, a new fact can change the useful next question or the basis of an earlier answer.

The first gain can be very small: one justified source allocation, one description comparison, a language relation that prevents a wrong continuation, or a localized reconstruction failure. An already sufficient source passage, MethodDescription or prior result is an ordinary exit. A language becomes worthwhile when maintaining these connected answers saves consequential repeated reconstruction; its existence alone establishes no such gain.

Several forces remain in tension: source fidelity and a usable synthesis; reusable knowledge and situation-specific judgment; enough preserved context and affordable reading; local repair and hidden cross-pattern dependence. The profile keeps serious alternatives visible. A direct description or small synthesis note may be cheaper. A stable source-processing sequence may be appropriate. Neither is excluded by the ability to unfold use under changing conditions.

ME.Preface:7.2 - Production and situated use are different contributions

The production side engineers source-grounded Method-description knowledge in pattern-language form. ME.4 recovers documentary contributions; ME.21 reconciles and allocates them; ME.23 architects the useful language; ME.24 challenges promised coverage and localizes refresh. ME.5/ME.8 supply Method qualification and one-Method description content when needed. ME.22 is used when an actual revision question requires separating content and form.

The situated-use side, ME.20, starts from the result needed now and follows only a contribution whose conditions support that use. A practitioner can use a finished language without performing its production Method. An author can repair one allocation without enacting all other production actions. The profile connects these uses; it does not merge their subjects into one Method.

The profile account concerns this arrangement of knowledge and uses. Its material relations include a description relying on an allocated claim, a reconstruction finding returning to that allocation, an alternative description supplying the same receiving use, and a source change invalidating a dependent current-use premise. Those relations matter because they change what may be used or must be reconsidered. They are not merely hyperlinks or positions in the publication.

A body may describe one Method, part of a description, or a neighboring evidence or maintenance question. Several bodies can concern the same Method; one source contribution can support several bodies. A source chapter, pattern, action row or publication Part is not automatically a part Method. Use ME.5/ME.7 and B.1.5 for an actual whole-and-part claim. Real smaller Methods can be parts when the whole-forming relations support that account; a holonic interpretation is not supplied by layout alone.

ME.Preface:7.3 - Production MethodDescription — Engineer a source-grounded MethodDescription in pattern-language form

The subject of this description is one reusable production Method: use role-qualified source contributions and current suppliers to engineer actionable Method-description knowledge as a pattern language, retain the grounds of its allocation, and challenge and refresh its promised source coverage. The result can contain several one-Method descriptions and neighboring contributions. Call that whole result one MethodDescription only when its exact subject and substantive claims satisfy A.3.2.

This account describes the production Method without establishing a decomposition into part Methods. The following actions and result dependencies explain its prospective performance. When the receiving use depends on a constituent Method, use ME.7/B.1.5 to identify it and establish its relation to the whole; B.1.5.EW recovers how its work is performed within the encompassing work. The Method’s identification does not establish that it has already succeeded in recurring production practice.

Inputs and applicability. Start with a named receiving practice and use, inspectable source contributions, their roles and limits, and the relevant current FPF/DPF supply. Documentary claims enter through ME.4. Observations, artifacts, logs and interviews about dated Work first require an A.3.1.MR recovery result; use ME.18 only for its remaining consequential evidence question. A returned candidate account retains rival explanations and gaps. If the receiving use or required source cannot be established, the first useful result is that exact blocker.

Reusable action. Select source depth by the question; recover source-local meaning; compare current supply and serious alternatives; reconcile the surviving contributions without inventing Method identities; allocate their useful claims; describe the needed Methods; organize independently useful pattern questions and material relations; then attempt the reconstruction the language promises. Preserve a direct-source remainder where it is sufficient and recoverable. Each action consumes only the results it actually needs. A missing condition can return the work to that question before the rest is complete.

Source-profile variation. Use the profile that matches each source and receiving claim:

F.0.1/F.1/F.0.2 govern source meaning, selection and conceptual synthesis. ME.21 consumes their results for the Method-specific allocation: reuse current supply, add or amend the professional contribution, retain a direct-source or unresolved remainder, or return a genuinely general question to FPF. The useful output states what changed and why, rather than merely listing source destinations.

Results and stops. The complete result for the selected use is an actionable language with identifiable description subjects, conditions, material relations, recoverable source decisions and an affected-refresh route. A smaller completed allocation, comparison or reconstruction result can be used independently without claiming that the whole language is complete. Stop a dependent use when its required basis is missing; preserve independently supported results. Do not promise corpus-complete coverage from a sample or gap-only pass.

Variation and identity. Source order, source profiles, tools, reader entries and representations may vary while preserving this reusable action and its source/evidence discipline. A change to the whole action, required allocation and source-return discipline, language result, reconstruction obligation or dependency direction reopens the Method identity through ME.5/ME.15. Changing a description or publishing tool does not by itself create a Method variant.

Enactment boundary. A prospective action description is not a dated Work occurrence or a WorkPlan. An account of an actual production attempt identifies its performers, conditions, support and observed results. During ongoing Work, A.15.7 supplies a separate next-action decision that names the chooser and performer. ME.11 can obtain trial evidence; ME.13 and ME.14 separately judge transfer and worth. The constructed application below makes the description inspectable but does not supply those empirical results.

ME.Preface:7.4 - Unfolding a use, including a changed situation

A practitioner recognizes the current difficulty, asks which result is missing and tests the conditions for the contribution that could supply it. An available earlier result may already suffice. New observations can change a current judgment, expose another missing result or make the present use stop. This is ordinary ME.20 use without an obligatory formal graph.

When a formal continuation answer is needed, A.22.CGUS supplies the stronger structural and case-judgment semantics. Identify its constituents, relations, constraints and use frame; preserve the difference between currently available, blocked and unknown continuations, including evaluation errors. A completed condition that does not satisfy a rule is not an unknown condition. A graph view alone supplies none of these judgments.

Changing facts within the same use frame requires a fresh applicable judgment. Changing the question, governing conditions or stop rule can require reidentifying the frame itself. Thus the situation is reconsiderable at each working move; its boundary is not mechanically reset after every action. Local order can still be required. The profile’s acausal emphasis means that one global causal or calendar route is not prescribed in advance, not that causes, agents, planning or causal inquiry disappear.

This differs from relying on one up-front assembled method package, but it is not a claim that all earlier SME required that package. Intention-sensitive, evolutionary and continuous-composition lines already provide important alternatives. PLUS-ME’s particular choice is the relation between source-grounded pattern knowledge, independently qualified Method semantics and situated result use.

ME.Preface:7.5 - Worked connected application — H, L and W

This is a constructed application, not a report of completed empirical validation. A Method engineer wants a small language for reviewing and adapting a Method description.

Handbook H, edition 3, §4, supports reuse of an earlier review after a display-only change. Paper L, edition 1, §2, limits that reliance to matching reviewed claims, question and qualification window. A returned MR account W, version 2, reports that a team shortened a warning; it preserves two rival explanations, harmless redundancy and a missed condition. The new language must not turn that report into an admitted shortcut Method.

First use. ME.4 preserves H and L source-locally; W remains a separately returned candidate account. ME.21 reuses ME.12’s existing coherence contribution and carries L’s narrower condition into the description. Tool-specific layout instructions remain at H. The allocation produces a conditional reuse answer and an unresolved W remainder, not a new Method count.

If that one description settles the receiving use, ME.8 is sufficient and the engineer stops. For recurring allocation, review and source-return questions, ME.23 connects independently useful entries: the review relies on the allocated condition, and a missing coverage relation returns to the affected source decision. This arrangement does not establish three parts of a review Method.

ME.22 compares earlier prose A with revised prose B that adds the matching-condition and source-return stop, then compares B with a table C preserving those same claims. Merely comparing A with C could not separate the added content from the new presentation. Textual comparison can reveal that A lacks a needed stop. A claim that C helps readers more than B needs an appropriate comparison of their actual use; the table’s appearance is not that evidence.

ME.24 reconstructs the promised reliance answer. A topic entry and source citation are insufficient if the condition cannot be recovered. Its first result names the missing condition or confirms recoverability only for this bounded case.

Changed condition, supplied only after the first answer. H becomes available only as excerpts. A new receiving use requires rechecking an argument outside them, and the retained allocation contains only its locator, not the argument. The recheck now has an unavailable basis. Return that dependent use to source recovery, use a separately justified sufficient basis, or narrow or stop it. Keep the earlier result with its historical basis, L’s independently supported condition and W’s unresolved status. Another pattern that copied the missing premise is affected even if its file did not change.

ME.20 continues from this newly missing result. If only source availability changed, reconsider the current judgment. If the reader instead asks whether publication is authorized, identify that new use and its required result. A prior review is not publication authorization. In actual Work, the chooser and performer remain explicit.

A useful answer to this case preserves the first action, condition and stop, distinguishes the three source roles, makes no invented part Method, and localizes reconsideration without losing another dependent use. A rehearsal of these answers tests the explanation. It does not measure production cost, human performance, transfer or causal superiority.

ME.Preface:7.6 - Practical checks, recurring failures and costs

Recognition and assurance answer different questions. First identify the missing result and a plausible contribution. Then check only the claims on which the actual use relies, with the evidence and independence that their conclusion needs. Do not treat finding the right heading, obtaining a graph path or reading all patterns as assurance.

For a production result, ask whether the receiving action and stop are recoverable; whether sources and candidate evidence retain their roles; whether each merge, split and omission has a reason; whether the language keeps Method identity separate from body allocation; and whether a changed premise has an identifiable return. When the promised use spans several patterns, challenge at least the material relation on which that use depends. Broaden a check when the dependency boundary is unknown, not merely because the language is large.

The recurring failures have distinct repairs. A chapter copied as a Method returns to recovery and qualification. A tidy graph that loses a condition returns to description content. A comparison that changes both content and form returns a bundled result, not a form advantage. A coverage table that counts topics returns to reconstruction. A source-access failure stops a required new recheck; it does not retrospectively falsify everything derived from the source.

Source familiarity, preference for a neat architecture and enthusiasm for pattern languages can bias all these judgments. Preserve the rival account and the cheaper direct route. AI-assisted recovery or comparison retains its model, input and interaction limits when they matter to the claimed result; fluency does not replace source access or independent use evidence.

The practical benefit is reusable source decisions and more local reconsideration. The burden is additional initial reading and maintenance of the few dependencies needed for return. In one bounded comparison with two clean-context AI readers, both the full situated-use body and a truthful entry-only alternative supported the required continuation. After a changed condition, the full-body reader reused its return guidance without another source opening; the entry-only reader reconstructed that boundary from two further source passages. This is a local reconstruction benefit, not a measured total-effort, correctness or human-performance advantage. The full body also requires its upfront reading and maintenance. Whole-production effectiveness remains unestablished. Use a simpler account when maintaining the language does not repay its burden.

ME.Preface:7.7 - Architectural Rationale and source comparison

Method Engineering keeps SME’s situation dependence and deliberate construction of reusable ways of working. PLUS-ME changes neither premise. It selects one profile in which patterns expose problems, forces, actionable contributions and useful relations, while Method identity and composition remain separately governed. The reuse unit is therefore not indiscriminately a source slice: it can be an independently qualified smaller Method, a description contribution or a neighboring non-Method answer.

This explains the distinct production results. Recovery must remain faithful even when allocation later rejects a proposal. Description comparison must not be replaced by either a cross-use representation profile or a judgment of Method worth. Language architecture must make material relations useful without creating parthood. Reconstruction must be able to find a missing contribution before a contradictory maintained claim and its owner are already known. ME.4, ME.21, ME.22, ME.23 and ME.24 keep these differences actionable; none requires an obligatory pipeline.

The following sources supply specific questions and alternatives, not a proof that this profile is universally best:

Alexander et al.’s A Pattern Language (1977) supplies the historical problem-first, connected-guidance idea. Minsky’s frame account (1974) connects situation knowledge, expectations and adaptation. The architectural analogy drawn here concerns those knowledge-use roles; historical descent of pattern languages from frame systems is not established by it. Declarative and case-management approaches, including CMMN 1.1, remain operational comparison targets, not the ontology adopted by this language.

The selected alternative is a profile within Method Engineering because its general qualification, architecture, representation and assurance questions remain shared. A separate framework would need a different justified field promise. A prose-only synthesis remains a serious lower-maintenance option; a fixed route remains legitimate under stable conditions. Reopen the profile choice when current supply removes a distinct result, reconstruction fails for a promised use, source conditions change, or the maintenance burden defeats the practical gain.

ME.Preface:7.8 - Relations and scope of the whole account

General Method Engineering remains directly available through ME.1–ME.19, with ME.22 available for non-pattern description comparisons. ME.20 supplies situated use; ME.21/ME.23/ME.24 add the production questions explained here. The documentary branch of ME.4 supplies both ordinary single-source and plural-source recovery.

FPF retains authority over Method and episteme identity, whole-forming relations, conceptual synthesis, representations, structures, CGUS, Work, evidence, next-action decisions and framework publication. An actual new general result returns to its FPF owner after professional and corpus-specific filling is removed. Local evidence can inform that return without making FPF normatively dependent on the local profile.

Professional and local profiles may specialize conditions, select use-bounded claims or reuse a contribution. These are different relations; overlap is not automatically a lattice and reuse does not merge identities. A formal mathematical or structural claim uses its applicable FPF governor. No sibling DPF, Guide corpus expansion or particular software tool is a prerequisite to an independently supported direct Method Engineering result.

ME.Preface:End