ME.23 - Choose Whether and How to Build a Problem-First MethodDescription Pattern Language
ME.23:1 - Problem frame
Use this when. The Method-related content has been recovered and allocated, but one linear description does not give recurring users the independent problem entries, neighboring decisions or source returns they need. You must decide which patterns and relations will make that content usable as a language.
The working reader is a Method engineer or domain-framework author. Start with a user’s question, such as “May I reuse this review after the source changed?”, and name the first useful result. Then identify the smallest body or cooperating set that can supply it.
The first useful result is a small language-architecture answer: the user’s problem entry, each needed contribution and its subject, the material relation between them, and the stop or return. One direct MethodDescription can be the correct answer. Use ME.8 without a language when it already serves the use; use E.11.PFP alone when only public arrangement or navigation is missing.
ME.23:2 - Problem
Source order, a procedure diagram or a repository taxonomy can become the pattern architecture without a separate decision. Every chapter is then treated as a Method part, every pattern as a MethodDescription, and every link as the next step in Work.
The opposite failure is a bag of useful patterns with no explanation of when they contribute together. A user must reconstruct prerequisites, alternatives, conflicts and source returns from private authoring notes. A whole-framework introduction can hide the same problem when it gives only labels and no practical answer.
ME.23:3 - Forces
| Force | Tension |
|---|---|
| Independent entry and connected use | A pattern should work from its own problem, while some results depend on neighboring contributions. |
| Reusable Method and broader language | One Method can need several descriptions; a language can concern several independent Methods and decisions. |
| Useful relation and invented order | Links help users continue, while adjacency does not establish time order, parthood or permission. |
| Shared explanation and repetition | Profiles need coherent reasons and shared conditions without copying each body’s Solution. |
| Progressive structure and first use | A formal structure can support later reliance, while an ordinary reader often needs only a clear question, action and return. |
ME.23:4 - Solution
Build the language from the questions it must answer and the results those answers consume. Keep Method semantics, pattern relations and publication arrangement distinct.
ME.23:4.1 - Select the smallest useful language
- Name the receiving uses. For each materially different use, state the reader, recognizable difficulty, first useful result and stop. Begin with one; add another only when it needs a different action or boundary.
- Recover the allocated content. Use ME.21’s source allocations or an already sufficient equivalent result. Preserve current suppliers, unresolved candidates and direct-source remainder. Do not infer a new Method from a source heading.
- Identify what each body describes or governs. Use ME.8 to describe how an admitted Method is performed or to improve an account of a proposed way while retaining its unresolved identification conditions. Keep neighboring selection, evidence, permission, architecture, representation and source-return questions under their own subjects. A body can cite those results without absorbing them.
- Compare the direct alternative. Try a direct description or existing pattern entry for the same use. Retain a new body or language relation only when it adds a warranted action, result, boundary or saved source reconstruction at acceptable burden.
- Assign the contributions to bodies. Give each body its own recognizable problem, useful move, worked case and stop. Put shared conditions and the reasons for the selected combination in the profile’s whole account; use exact returns to inherited body answers.
- Name the material relations. State in ordinary language which result another use consumes, what condition enables that use, what is an alternative, what conflicts and where a failed or missing result returns. Apply the defining FPF relation when a stronger relation claim is needed.
- Provide direct reader entries. A reader should reach the relevant full body from a problem question without reading the complete production account. Whole-use explanation remains available for choosing, combining or adapting the language.
- Challenge the proposed arrangement. Use ME.24 to attempt reconstruction and a changed-source return. Use ME.22 only when a material claim about content or representation advantage remains. Keep a direct-description or smaller-language answer when it is sufficient.
The list is an authoring aid. It does not prescribe the order of every user’s Work.
ME.23:4.2 - Keep the described wholes separate
A MethodDescription has one admitted Method as its exact subject. A source-grounded language may publish such a description across several bodies when their bounded claims jointly describe that Method. State that subject and the claims included; do not infer membership from a coherent book or a shared title.
A profile account concerns the selected pattern/Method arrangement for its declared uses. It can include several MethodDescriptions and neighboring results. A separately addressable description of the production Method excludes independent situated-use and general profile-relation claims. Sharing a carrier does not merge those epistemes.
Method parthood is another claim. Independently identify the proposed whole and smaller Methods, then use B.1.5 for their whole-forming relations, joins, bounds and failure conditions. In the absence of that result, a useful action/result architecture remains prospective. Do not make the pattern inventory stand in for the missing composition.
ME.23:4.3 - Make each relation say something useful
Use the relation that changes the receiving action. The following are common questions, not a required universal relation catalogue:
| Relationship question | Useful statement |
|---|---|
| Result dependency | This description review consumes the qualification of these claims; if it is missing, return to that qualification. |
| Alternative | Either representation can serve this action under its stated loss limits; choosing one does not prove the other false. |
| Source support | This assertion relies on this recovered passage for the named use; changed or unavailable basis reopens that reliance. |
| Conflict | These candidate conditions cannot both govern the same selected use; retain the conflict for the owning decision. |
| Reuse or specialization | This profile reuses the general action and adds this source-specific condition. |
| Method composition | This independently admitted Method is a part of that whole under the B.1.5 result. |
| Publication grouping | These bodies are shown together to help discovery; their display order makes no stronger relation claim. |
A formal CGUS is appropriate only when that structure is itself needed. A.22.CGUS supplies the constituents, selected obtaining relations, applied constraints and named use frame, as well as potential branching and case-judgement requirements. Plain alternatives and conditions do not automatically admit that structure. ME.20 supplies ordinary situated continuation and its optional formal branch.
A changed fact can change a continuation judgement under the same frame. A changed question, admissible action or stop can require reidentification. The user or capable system assesses the new situation. During ongoing Work, A.15.7 supplies the next-action decision.
When the promised use includes performing or learning a Method, show its relevant vertical as well as result dependencies. At a selected moment, what constituent action is enacting what encompassing work, and what changes in that action when a condition of the whole changes? B.1.5.EW supplies this recovery. Show the capability, support and combined resource conditions that the DPF’s own bodies leave to another contribution. Use a representative case where a missing intermediate performance changes the continuation; do not require an exhaustive stack when its understood parts cannot change the use. B.1.5.RS supplies the distinct comparison when a constituent is replaced across encompassing uses.
ME.23:4.4 - Explain the profile at its own scope
Use all twelve substantive E.8 functions for the connected account: working situation, problem, forces, selected solution, grounding, bias, practical checks, recurring failure, consequences, Architectural Rationale, source comparison and relations. E.11.PFP governs where readers reach those answers. An inherited answer can be cited precisely; shared whole conditions and profile-specific consequences still need an explanation.
If a language is claimed to expose more structure to its reader, use ME.22 with C.2.8 for that specific comparison. Select the dependencies, alternatives or stops the reader needs, and distinguish new content from a different expression of the same claims. Identify the actual preparation, help and source returns. More patterns or links do not establish more extractable structure, and a larger amount does not establish that the language is worth its reading burden. Keep the direct description or smaller language when it suffices.
Distinguish relations across scales. A specialization narrows conditions while retaining the relevant general claims. A bounded-use projection selects claims for a reader. Reuse can connect several profiles. Method composition establishes actual parts. A publication group provides navigation. There is no fixed maximum number of scales, and overlap does not establish a mathematical lattice; use C.29 only for that qualified representation.
ME.23:5 - Archetypal Grounding
ME.23:5.1 - From a review paragraph to three independent questions
This is a constructed case. An engineer has an admitted Method for checking a Method-description claim against its source and qualification basis. A use-bounded ME.8 description of that Method already explains the checking action. The new language must additionally help recurring users decide how unlike source contributions were allocated and what to revisit after a source change.
The proposed arrangement is:
| Reader’s question | Contribution | Material connection |
|---|---|---|
| What did we decide to carry from these sources? | ME.21’s allocation answer | The review can cite the allocated claim and its retained conditions. |
| Do the relied-on claims still agree with their maintained basis? | ME.12’s coherence answer | A contradiction returns to the maintained claim that owns it. |
| What promised source contribution can no longer be recovered? | ME.24’s reconstruction answer | A missing allocation or source relation returns to that affected question before dependent reuse. |
These are independently useful entries. Their colocation does not make these pattern subjects parts of one review Method. The ME.8 description retains its one-Method subject; the profile explanation concerns the broader arrangement.
For a user who already has the needed allocation and only one contradictory claim, direct ME.12 use is enough. A user investigating an unexplained coverage loss starts with ME.24. The language is useful because the first result and return are visible at either entry, not because all three rows are traversed.
ME.23:5.2 - A source-change return
The allocation relied on an argument now unavailable for a required new recheck. The earlier answer remains preserved, but the dependent current-use claim has no recoverable basis. The reader returns only that claim and its source relation. A separately supported allocation and review remain usable.
If the user’s question changes from reviewing the description to authorizing publication, it is another receiving use. The language points to the applicable publication result; a completed review is not that authorization.
ME.23:6 - Bias-Annotation
A procedure-shaped source encourages a fixed workflow; a graph tool encourages graph-shaped explanations. Start with the actual questions and their result dependencies before choosing either form.
The worked arrangement demonstrates language and identity distinctions. It is not evidence that every Method engineer benefits from the same grouping or that the resulting profile is an enacted composite Method.
ME.23:7 - Conformance Checklist
- The language begins from recognizable uses and first results.
- Each body has a recoverable subject, practical contribution and ordinary stop.
- Every MethodDescription claim identifies its one admitted Method.
- Each material relation states what it changes in use and retains its own governing basis.
- Direct descriptions and sufficient existing entries remain available.
- The whole/profile account explains shared conditions and reasons without replacing the full bodies.
- Reconstruction and changed-condition use can return a localized failure or an honest wider gap.
ME.23:8 - Common Anti-Patterns and How to Avoid Them
| Misstep | Repair |
|---|---|
| One pattern equals one chunk equals one Method part. | Identify the body subject and qualify Method parthood separately. |
| Every link means “do this next”. | State the result, condition, alternative or return actually meant. |
| A profile is called one MethodDescription because it has one title. | Identify its exact subject and separate broader arrangement claims. |
| Twelve headings replace a whole explanation. | Answer the content questions at the declared scope, using inherited answers where sufficient. |
| A complete reading route becomes compulsory before first use. | Provide a direct question-to-body entry and an affordable stop. |
ME.23:9 - Consequences
The language supports problem-first reuse and makes its connections inspectable. Users can select a small contribution, follow only a necessary dependency and revisit affected claims after change.
The cost is maintaining the cross-pattern explanation and relations. A direct description is preferable when that extra structure does not change recurring action or save meaningful reconstruction.
ME.23:10 - Architectural Rationale
A source-to-language architecture lies between source allocation and situated use. It must show how independently useful descriptions and neighboring results contribute together while preserving their different subjects. ME.8 alone does not decide that whole arrangement; E.11.PFP alone does not supply its Method-specific content.
The selected structure can be useful without an admitted composite Method or a formal CGUS. Progressive exactness lets ordinary users act from a clear result and stop while preserving a path to the stronger claims when a later use needs them.
ME.23:11 - SoTA-Echoing
Alexandrian pattern languages provide the historical problem-first, relational and generative idea. Ralyté, Deneckère and Rolland’s SME Map (2003) already supports on-the-fly construction; continuous SME composition and enactment is a serious implemented alternative. Adopt their adaptive-use pressure, not a claim that unfolding begins here.
Current E.8/E.11.PFP supply individual and whole-account form; A.3.1/A.3.2/B.1.5, A.22.CGUS and ME.20 supply the separate identities and use results. This pattern adds the Method-specific language arrangement after source allocation.
Against the cheaper direct description in the worked case, the language adds independently reachable allocation and reconstruction questions. It earns that cost only when those questions recur or change action. No general advantage over prose, a method base or a fixed suitable route follows from the architecture. Reopen when a direct entry becomes sufficient, a relation loses its basis, or changed use makes the grouping burdensome.
ME.23:12 - Relations
- ME.21 supplies semantic allocation; ME.5/ME.7 and ME.8 supply Method qualification and description.
- E.8 and E.11.PFP govern body and whole-account form; C.2.1 governs retained account identity.
- B.1.5 governs actual Method composition; A.22 and A.22.CGUS govern selected and unfolding structures.
- ME.22 supplies a bounded description comparison when content or representation claims matter, using C.2.8 when structural recovery is the selected question.
- ME.24 tests reconstruction and affected refresh; ME.20 supports situated use without requiring production.
- ME.9 and C.37 retain representation selection; ME.15 retains Method-variant and non-variant maintenance.