ME.21 - Reconcile and Allocate Source Contributions for Method Use
ME.21:1 - Problem frame
Use this when. You have recovered useful Method-related material from several sources, but still have to decide which contributions belong together and where they should be used. A handbook, research paper and account recovered from practice may use the same words for different actions, or different words for the same useful move.
The working reader is a Method engineer building or revising descriptions, a repertoire or a pattern language. Begin with one disputed allocation: which recovered contribution should this description or pattern carry, and what would be lost by placing it there?
The first useful result is one justified allocation. For example: “Use the existing coherence-checking Method; keep this source’s narrower qualification window with the affected description claim; leave the observed shortcut as a candidate account.” Stop there if it settles the receiving decision.
Use an already sufficient F.0.2 synthesis or existing pattern result directly when no Method-content allocation remains. ME.4 recovers documentary contributions; A.3.1.MR, and conditionally ME.18, recover accounts from Work evidence. ME.21 starts from their results, not from an unread corpus or raw observations.
ME.21:2 - Problem
Recovered material rarely arrives in reusable units. One chapter mixes a Method, a tool recommendation and a permission condition. Two sources agree on the main action but disagree on when its result may be reused. A practice account records a shortcut without establishing that the shortcut is a reusable Method.
A vocabulary crosswalk or chapter-to-pattern table does not decide these differences. Premature merging hides conditions; excessive splitting creates duplicate accounts; assigning every remainder to a new pattern turns source coverage into a publishing quota. Later users then cannot explain why a contribution was included or which source change requires repair.
ME.21:3 - Forces
| Force | Tension |
|---|---|
| Reuse and fidelity | Shared guidance saves reconstruction, while a source-local difference may change the action or stop. |
| Existing supply and useful remainder | FPF and ME already provide much of the answer, while a specialized condition or constructive move can remain. |
| Small allocation and connected account | One decision may need one row, while several dependent allocations need an inspectable explanation together. |
| Source authority and Method identity | A respected source can support a claim without admitting every listed step as a Method. |
| Convergence and disagreement | Similar contributions can share a description, while incompatible meanings need a contrast or an unresolved question. |
ME.21:4 - Solution
Reconcile meanings before assigning destinations. Preserve every difference that changes the receiving Method use, and make the allocation’s source return recoverable.
ME.21:4.1 - Work one allocation
- Name the receiving use and contribution. Identify the description, Method question or pattern-language use being changed. Take the recovered source claim together with its difficulty or opportunity, proposed action, result, conditions and source location.
- Keep the input roles distinct. A documentary claim remains what that source asserts. A returned MR account keeps its candidate, rival and evidence limits. A current FPF/DPF result keeps its declared scope. A source’s report that work occurred is not independent occurrence evidence.
- Resolve only the meaning difference that matters. Use F.0.1 when a source expression is ambiguous, F.1 when the source cut is insufficient, and F.0.2 when cross-source synthesis is needed. Consume its provisional synthesis, contrast or unresolved-inquiry result, including its locator, source edition and receiving disposition; do not replace that result with a similarity score.
- Subtract the current answer by value. Open the current FPF/ME supplier that appears to cover the contribution. Compare the practitioner question, action, first result, applicability and stop. Use the supplier directly if it answers those positions. When a source adds a warranted Method-specific condition or move, retain that remainder and explain its receiving use.
- Decide whether the contributions can share an account. Compare reusable action, participant meanings, preconditions, result, variation and stop. Merge supported common content while retaining different conditions. Split incompatible actions or statuses. Keep an unresolved alternative when the evidence cannot distinguish them. ME.5 and ME.7 settle any Method or whole claim needed by the allocation.
- Assign the contribution and its remainder. State what is reused from current supply; what is added to or changes a Method description or pattern; what remains direct source material; and what is unresolved. Return a transdisciplinary question to FPF only after the Method-, corpus- and publication-specific content has been removed.
- Make the decision usable and revisable. Give the reader the contribution, reason, destination, retained difference, source return and next action. If a later user will cite the allocation, keep a stable local locator with its edition. Name the source or supplier change that reopens it.
A one-contribution answer is enough. Expand to several allocations only when their overlap, omissions or shared conditions change the language or receiving decision.
ME.21:4.2 - Preserve what the destination cannot carry
A pattern may present the reusable action and still leave a worked derivation, local convention, dataset or detailed instruction at its source. State what remains there and how to recover it. A promised self-contained use cannot depend on an undisclosed omission.
When contributions merge, retain the reason that their common action is usable under the resulting conditions. When they split, preserve the action-changing difference and the relation between the resulting accounts. Shared terminology, publication order and apparent granularity are not sufficient reasons for either decision.
The allocation concerns source contributions and their uses. It is not a Method-composition result. Actual Method parts are independently identified Methods related through B.1.5; a pattern body, tool, source fragment or source-recovery step is not a part by position.
ME.21:4.3 - A compact retained answer
For a reusable allocation, this amount of information is normally enough:
| Position | Question answered |
|---|---|
| Receiving use | Which Method-description or pattern-language question does this allocation settle? |
| Source contribution and role | What is being carried from which passage, edition or returned account? |
| Current supply | Which existing result answers the reusable part, under what limits? |
| Reconciliation | What is shared, different, merged, split or still unresolved, and why? |
| Destination and remainder | What changes in the receiving description or pattern, and what remains elsewhere? |
| Return | Which changed premise reopens the allocation, and where should the reader return? |
Use ordinary prose instead of a table when it is clearer. A retained allocation is a claim-bearing account about the named allocation question; its claim content, subject and effective reference scheme determine its C.2.1 identity. Its locator is a recovery aid, not a Method identity or an acceptance decision.
ME.21:5 - Archetypal Grounding
ME.21:5.1 - One review action, two conditions and a candidate shortcut
This is a constructed case. A Method engineer is preparing guidance for reusing an earlier review of a Method description.
- Handbook H, edition 3, §4, says to reuse the earlier review when only the description’s display changes.
- Paper L, edition 1, §2, says that reuse also depends on the same reviewed claims, question and qualification window.
- Returned account W, version 2, reports a team that reused a review after shortening a warning. It retains two rival explanations: the warning was redundant, or the team missed an important condition.
The documentary dossier preserves H and L separately. W remains candidate evidence. Current ME.12 already supplies the coherence check and owner-specific correction; ME.15 distinguishes a description change from changed reusable Method semantics.
The engineer’s allocation is:
| Contribution | Allocation and practical reason |
|---|---|
| Recheck a relied-on claim against its prior basis | Reuse ME.12. The sources do not require another general coherence Method. |
| Reuse the earlier review for a display-only change | Carry it as a conditional use of that result: the relied-on claims, question and qualification window must still match. H’s shorthand does not erase L’s limit. |
| Shortening the warning | Retain W’s rival accounts and the missing comparison. Do not create an admitted “shortcut Method” from one reported occurrence. |
| Layout instructions for the handbook’s publishing tool | Keep them in H. They do not belong in the reusable Method claim. |
The first useful result is the conditional reuse answer, not a new pattern count. A description author can now state the condition and the exact return to ME.12.
ME.21:5.2 - A changed source does not erase a former result
Later, H is available only as excerpts. The retained dossier contains merely a locator for the argument used by the allocation, and a new receiving use requires checking that argument. Return that recheck as unavailable and lower the dependent use. Preserve the earlier result with its historical basis, L’s independently supported condition and unrelated allocations. Reopen only what relied on the missing argument.
If the complete argument had already been preserved with a suitable basis, loss of current website access alone would not establish that the earlier claim was wrong.
ME.21:6 - Bias-Annotation
A source familiar to the engineer can become the vocabulary into which every other source is translated. Counter this by stating each source’s action-changing meaning before merging. A desire for a neat language can also make every contribution look like a new Method; retain the non-Method and unresolved material that the receiving use actually needs.
The worked case illustrates allocation decisions. It does not establish the effectiveness of review reuse in an external project.
ME.21:7 - Conformance Checklist
- The receiving use and the contribution being allocated are recognizable.
- Source assertions, recovered candidate accounts, current supply and occurrence evidence retain their different roles.
- Current supply was compared at the action, result, condition and stop that matter.
- Every merge or split preserves its semantic reason; unresolved differences remain visible.
- The destination states the useful change and the direct-source or instructional remainder.
- Method identity and composition claims have their own basis.
- A changed premise leads to an identifiable reconsideration or stop.
ME.21:8 - Common Anti-Patterns and How to Avoid Them
| Misstep | Repair |
|---|---|
| One source chapter becomes one Method or pattern. | Recover the contributions and decide their subjects before allocation. |
| Similar wording is treated as the same action. | Compare participants, result, conditions and stops; retain a contrast when they differ. |
| “Already covered by FPF” removes the specialized useful move. | Show the current answer and the remaining domain filling at the same receiving use. |
| A source gap is treated as a false claim. | Preserve the unresolved inquiry and state the source action that could settle it. |
| A source-reference list stands in for an allocation. | State what changes in the receiving description or pattern and why. |
ME.21:9 - Consequences
The engineer gains a language or description whose source decisions can be challenged and repaired locally. Reuse is more selective: some material disappears from the new body because a current supplier already answers it, while useful differences survive instead of being averaged away.
The cost is retaining the few source and dependency facts needed for later reconsideration. For a one-off question that F.0.2 or a direct source already closes, another allocation account adds no value.
ME.21:10 - Architectural Rationale
Source recovery answers what the material says. Conceptual synthesis answers what a cross-source comparison warrants. ME.21 uses those results to settle a Method-specific distribution: what reusable action and condition belong in which description or pattern, and what must stay outside.
Keeping this result separate from ME.4 lets documentary recovery remain faithful even when a later allocation rejects a source proposal. Keeping it separate from Method admission prevents a placement decision from creating a Method. Retaining one small allocation before a corpus-wide map keeps the first useful result affordable.
ME.21:11 - SoTA-Echoing
The current best-known approach for this question combines source-local conceptual comparison with Method-content and use analysis. F.0.2 supplies the former; ME.4, ME.5, ME.8 and the other direct ME results supply their professional subjects. In the H/L/W case, the added allocation preserves a usable conditional review answer, rejects an unsupported shortcut-Method identification and leaves tool instructions at their source. A generic synthesis note can be sufficient when it already contains those destinations and returns.
Daalhuizen and Cash’s Method Content Theory (2021) supplies questions about goal, procedure, rationale, framing and mindset. Stacey et al. (2025) reinforces the need to retain the knowledge and use conditions around procedural guidance. Adopt these as source questions; do not turn their different models into a universal field schema or FPF parthood test.
The professional allocation is a local synthesis, not a claim of priority over SME or conceptual synthesis. Reopen it when current supply makes a separate result unnecessary, a source difference defeats a merge, or maintaining the allocation costs more than the source reconstruction it saves.
ME.21:12 - Relations
- ME.2 supplies repertoire and lineage; ME.4 supplies documentary recovery.
- A.3.1.MR and conditionally ME.18 supply recovered Work accounts with their limits.
- F.0.1/F.1/F.0.2 govern source meaning, selection and conceptual synthesis; E.4.DPF governs framework-contribution subtraction.
- ME.5/ME.7 qualify the Method claims; ME.8 authors a description or improves a candidate Method account for a named use, retaining its identification status.
- ME.23 uses the allocation to architect a language; ME.24 challenges its recoverability and refresh reach.
- ME.12 and ME.15 receive contradicted claims and variant or non-variant maintenance questions.