RMP.10 - Reconstruct a Candidate Method Account from Practice Evidence
Status: Stable
Type: Method pattern
Primary working result: a claim-to-evidence dossier that connects each proposed account of a reusable practice to the evidence for it. Include significant contradictions, rival explanations, limits and the results of any further checks performed. Sometimes the evidence establishes only an occurrence, a local workaround or tool behavior, or leaves the grouping unresolved.
RMP.10:0 - Use This When
Use this method when ordinary recovery through A.3.1.MR, or a usable result of that work, leaves a material reconstruction question and answering it warrants a larger evidence programme. You may need to distinguish settings, disputed variants, tacit cues or judgements, gaps in the records, or the reach of an account under changed conditions. A question about past practice can warrant the work in its own right.
Identify what the recipient needs to know about a possible reusable practice. Select the claims whose content, scope or support matters to that use and the forms of evidence that can distinguish the plausible answers.
A first result connects each claim to the observations that could support it, contradict it, distinguish variants or justify a narrower statement. Use this claim-to-evidence matrix to select cases or sources and to estimate the specialist work still needed.
Use an existing account or a description of the observed work directly when it answers the question. When making a stronger reconstruction, distinguish what occurred from the later hypothesis about a reusable Method. Use an instruction as evidence of what it prescribed and event records according to what they recorded. A.3.1 governs identification of a Method.
RMP.10:0.1 - Working Distinctions
| Evidence or result | Contribution retained here | Boundary |
|---|---|---|
| occurrence observations and artifacts | Overt actions, results, versions, coordination and traces for a particular Work occurrence. | Recurrence supports a claim about observed behavior. Identifying a Method requires the applicable identification grounds. |
| Critical Decision Method (CDM) probe | A participant’s recalled cues, options, judgements and counterfactual reflections on a critical incident. | Account for recall and interviewer effects. Establish logged events from their records. |
| event-log analysis | Recorded recurrence, sequence, deviation and conformance under the declared meanings of the log fields. | To infer intent or tacit contribution, establish what evidence bears on it. A recording of events and an instruction can serve different claims. |
| contextual observation or protocol elicitation | Evidence of coordination, workarounds or reasoning that the other selected sources leave open. | Choose and qualify each operation for its own purpose and risks. Cite the source that supports it. |
| expert synthesis | The matrix, sampling for relevant variation, comparison of apparent contradictions by scope, and choice of checks and stopping conditions. | Attribute these choices to the practitioners combining the evidence. |
| candidate Method account | a scoped episteme about a possible reusable way of doing | Method identification remains with A.3.1 |
RMP.10:1 - Problem Frame
Logs capture events visible to the instrument. Instructions describe intended action. Interviews can favour memorable episodes. Records of success can overlook recovery work or practices used by a minority. For an unresolved claim, identify which information is missing and which source could provide it.
Compare the contribution a specialist inquiry could make to the content, scope or grounds of the candidate account with the work it would require. If ordinary recovery answers the receiving question, use its result.
RMP.10:2 - Problem
A recurring log entry can be mistaken for a reusable Method and a vivid recollection for a common practice. Counting accounts can conceal a variant used in a few settings or an important failure. Identify what evidence would distinguish the alternatives and when enough has been established.
For each consequential claim, identify its supporting evidence, what could count against it and which uncertainties affect the intended use.
RMP.10:3 - Forces
| Force | Tension |
|---|---|
| Tacit contribution | Important cues and judgments may be absent from records, while elicitation can distort them. |
| Heterogeneity | Differences among performers and settings can distinguish variants. Sampling further examples of the same conditions may add little relative to its cost. |
| Contradiction | Variants may be real, while some disagreement is error or incomplete evidence. |
| Tool visibility | An event log can identify the events and fields it captured. Coordination or intent may require evidence beyond those fields. |
| Further discrimination | A case withheld from account development can test a prediction under new conditions. Record the predictions before examining the case and weigh the expected contribution against the cost of obtaining it. |
| Specialist burden | A consequential reconstruction may justify sampling and analysis across several sources. Ordinary recovery can be sufficient for a narrower use. |
RMP.10:4 - Solution
If the evidence strategy remains open, RMP.2 helps choose a design or a justified stop. Use an adequate supplied design or trace directly. RMP.3 addresses operational choices and RMP.4 the actual observations, elicitation records and logs with their access conditions. Here connect each uncertainty about a reusable practice to evidence capable of resolving it. Keep a variant tied to its setting when the evidence supports the difference, and report the account the combined material warrants.
Arrange the evidence by the claims that matter to the receiving question. Identify each source’s contribution, examine disagreements in their settings, and select a further check when the result it can provide warrants the effort. Return the scoped accounts or the narrower conclusion that the material supports.
RMP.10:4.1 - Pattern-Use Unfolding
- Identify the use and the unresolved claims. What matters about the intended result, entry conditions, reusable operations or invariants, cues and judgements, participants, capabilities, information, artifacts, support, variation, recovery or stopping conditions? Include the aspects needed for the question.
- Connect each claim to evidence. State which observations could support or contradict the claim, distinguish variants or justify a narrower conclusion. Explain how the proposed evidence could discriminate among those outcomes.
- Sample for relevant variation. Select cases that could discriminate among accounts. Relevant differences may include success or failure, routine or exceptional work, performer, setting, tool or provider. Look for cases that could challenge an account developed on a convenient sample. If access prevents that comparison, limit conclusions accordingly.
- Use each form of evidence for its claim. Observations and artifacts can establish overt actions and results, CDM can recover recalled critical-incident judgements, and event-log analysis can establish recorded recurrence and deviation. Use contextual observation or protocol elicitation for a specified gap, allowing for the risks of that method.
- Trace claims to occurrences. Identify the occurrence behind each consequential observation, using existing records where adequate. Preserve important missing fields, observer effects, limits of recall, tool coverage and source access. Then determine what can be generalized across occurrences.
- Examine contradictions in context. Compare performer, setting, outcome and evidence form. Correct an established error. Ask whether the same reusable rule permits both observed performances, for example through a parameter or conditional branch. If the evidence supports one shared rule, retain it and state which conditions explain the difference. If a shared rule and independently adopted instructions both fit what was observed, retain both reconstructions until evidence distinguishes them. Propose separate variants when the evidence supports a difference in the reusable operation, and specify where each applies. When the explanation remains open, retain rival reconstructions, narrow the claim or describe the observed events.
- Decide whether to obtain more evidence. Identify what remains unresolved and which attainable result could matter. Include access, practitioner capacity, delay and the whole cost of acquisition. If a check of prediction or transfer justifies a held-out case, state each serious rival’s predictions about cues, decisions, variation and result before inspecting it. To interpret a completed check, compare the observations with predictions documented before the case was seen. For another claim, a source comparison or targeted elicitation may be more informative. Use sufficient existing evidence or state the limit if the needed check is out of reach.
- Finish at the supported scope. Return the accounts and the uncertainties that bear on their use. Rivals can remain when choosing between them would add nothing material to the question. If an important uncertainty remains, state the resulting limit and, where a use is proposed, whether it needs narrowing or deferral. The supported result may be a Work description, a local workaround, tool behavior, or an unresolved grouping of events.
RMP.10:4.2 - Record the Result
| Result position | Required content |
|---|---|
| receiving question | The situation and intended use, the candidate accounts and what remains unresolved. For a decision, include its consequences. |
| claim-to-evidence matrix | For each material claim, identify what observations could support, contradict or narrow it, distinguish variants, and show when the evidence will answer the question. |
| sample and occurrences | Relevant variation, the occurrences examined, source access, missing fields and limits of the evidence. |
| synthesis | Report the accounts and their scope, the variants or rivals retained, how the evidence explains any disagreements and what remains unresolved. Attribute the steps that combined the sources. |
| further checks, when relevant | The open claim, the contribution a check could make and its cost. For a completed check, give the result and remaining uncertainty. For a held-out case, distinguish predictions made before inspection from what was observed and revised. |
| return | The scoped accounts or narrower result, its evidence and limits, and the conditions for reconsidering it where relevant to use. |
RMP.10:4.3 - What Changes in Practice
Teams can distinguish what a sequence records from a candidate explanation of the practice, and what an interviewee recalls from what recurred. A comparison across settings can yield two supported variants. The receiving practitioner can use that result without having to infer a universal rule.
RMP.10:5 - Archetypal Grounding
RMP.10:5.1 - Ordinary A.3.1.MR Stop
Suppose a maintenance team has six calibration Work records linked to their sources. They use the same released instruction, input schema, equipment configuration, decision authority and meaning of the result. One failed record shows the missing-input stop described by the candidate account. The team needs a source-traceable account to compare two instructions. No unresolved cue, variant or question about transfer bears on that comparison.
A.3.1.MR returns the provisional candidate account for this use, its sources, any substantive rivals and significant limits. That result suffices for the instruction comparison. Interviews, process mining or a held-out prediction would add effort without resolving a relevant uncertainty here.
RMP.10:5.2 - Genuine Escalation: EC-417 Evidence Reconciliation
In this constructed case, ordinary records leave open whether internal and supplier-originated evidence reconciliation follow the same rule or require different branches. The distinction matters to evidence closure on EC-417. Case access and practitioner capacity make a larger inquiry worthwhile. The team uses twelve cases to develop accounts and reserves a thirteenth to discriminate among them.
- four firmware-only and four internal harness-plus-firmware releases accepted versioned provisional pinout evidence before safety closure;
- four supplier-originated releases required signed evidence at closure;
- four reconciliation boards were observed;
- CDM probes involved two supplier, two software, one hardware, and one safety practitioner; and
- a thirteenth supplier-originated change was reserved unseen for the held-out discriminator.
| Evidence move | Scenario contribution | Limit retained |
|---|---|---|
| observation and artifacts | Observed evidence versions, board records, integration bundles, approval states and closure results. | These establish what was visible in the cases examined. Population rates and unrecorded judgements require other grounds. |
| CDM probes | cues, considered options, judgments about provisional versus signed evidence, and counterfactual reflections in critical incidents | retrospective recall and interviewer effects remain |
| event-log analysis | Recorded recurrence and deviations in evidence-version, integration, approval and closure events. | Interpret the fields by their event semantics. Inferring intent or a reusable rule needs appropriate evidence. |
| expert synthesis | Choice of twelve development cases and one held-out case, an internal/supplier split, the contradiction rule, the test of rivals and the stopping judgement. | These are the reconstruction team’s choices in this example. |
Before inspecting the thirteenth case, the team recorded three rival predictions:
| Account or rival | Cues and decision predicted | Variation and result predicted |
|---|---|---|
C-Evidence-Reconcile-Internal applied beyond its observed scope | internally controlled versioned evidence would be the decisive cue; the internal reconciliation role could decide the branch without a distinct supplier approval | supplier origin would not change the branch; closure could proceed from the internal reconciliation result without signed supplier approval |
C-Evidence-Reconcile-Supplier | supplier-owned configuration and restricted geometry would be decisive; supplier responsibility and signed approval would remain required for closure | reversible early integration could occur, but a signed-delta comparison and affected verification would precede either closure or an explicit missing-approval stop |
R-Rig-Capacity-Only | Lack of rig capacity would trigger the hold and the decision to wait for the next slot. | The same branch would apply to internal and supplier changes, and the hold would clear when rig access returned. |
In the held-out case the team found supplier-owned geometry, restricted provider access and available rig capacity. The team allowed reversible early integration and withheld closure pending signed supplier approval. It required a signed-delta comparison and one affected verification, then closed after approval arrived. Those observations fit the supplier-scoped predictions. The hold despite available rig capacity contradicts the capacity-only rival for this case. The requirement for supplier approval contradicts extrapolating the internal account to this case.
Retain C-Evidence-Reconcile-Internal for the eight internal cases and C-Evidence-Reconcile-Supplier for the supplier-owned configuration with the signed-evidence branch. Rig availability remains a support condition. Evidence about the approval requirement distinguishes the accounts even though internal cases were more numerous. The one held-out supplier case leaves transfer to other suppliers, other configuration classes and cases of missing approval uncertain. The result is a pair of candidate accounts. Identification of a Method, effectiveness and population frequency would each need further grounds.
RMP.10:5.3 - A Specialist Programme Can Finish without a New Case
A retired repair service used two routing practices. Ordinary A.3.1.MR recovery from mixed logs and instruction editions leaves two possibilities for an urgent route, a repeatable cue-based branch and a supervisor override. A museum archive wants a qualified comparison of these accounts for the final year of the service.
Distinguishing the missing cue would change the archive’s comparison enough to justify the source work. The team selects dated routing sheets and critical-incident interviews with two available former dispatchers. The sheets record whether replacement stock was present. The logs record the chosen route. Linking both to the same occurrences shows that the disputed route accompanied absent stock in the accessible cases. Both dispatchers recall using the stock cue, and each describes an exception that required a supervisor. The sheets and logs support the recorded association. Attribute the recalled reasons and exceptions to the interviewees, within the limits of recall.
The archive can compare a stock-conditioned candidate branch and a reported supervisor exception with the earlier instruction. Return the source links, limits of recall and gaps outside the accessible cases. The service has closed. A new simulation would examine present performance under changed conditions. It could not supply an observation of the disputed historical occurrences.
The reconstruction answers the archive’s question at the supported scope. If a later operator proposes reusing the branch, examine its fit for the new conditions and what the earlier evidence can support there.
RMP.10:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
|---|---|---|
| trace bias | A recorded sequence is treated as a complete description of the Method. | Establish what the log recorded and identify any further grounds the claim requires. |
| interview bias | A memorable explanation is treated as sufficient proof of a general practice or its cause. | Establish which incidents the interviewee reports and what their account can support given its scope and the limitations of recall. For a stronger recurrence or causal claim, identify any further evidence it needs. |
| majority bias | The largest variant erases a competent minority or setting-specific branch. | Resolve contradictions by performer, setting, outcome, and evidence form. |
| method-brand bias | The name of one evidence method is taken as authority for the whole synthesis. | Attribute each sourced operation and identify the reconstruction team’s contribution. |
| programme bias | The team keeps collecting cases after the question has an adequate answer. | Tie sampling and stopping to the receiving question and the consequential claims still open. |
RMP.10:7 - Conformance Checklist
- Ordinary recovery or its supplied result leaves a reconstruction question important enough to warrant the specialist work.
- The matrix shows what evidence could distinguish the consequential claims and why the selected cases or sources cover the relevant variation.
- Each selected form of observation, artifact, elicitation, log analysis or synthesis contributes within its evidential limits.
- Claims of actual performance can be traced to the corresponding occurrences.
- The treatment of contradictions reflects their scope, evidence and remaining uncertainty.
- Any further check addresses an uncertainty that matters to the question and has an attainable contribution worth its cost.
- For a completed held-out check, the record distinguishes the predictions made before inspection from observations, surprises and revisions.
- Material variants and rivals have an identifiable scope and evidential basis.
- If the evidence establishes only an occurrence, local workaround or tool behavior, the result says so. If the observed activities cannot yet be grouped into a candidate Method account, the grouping remains open.
- The conclusion distinguishes occurrence evidence, a proposed reusable account, a MethodDescription, identification of a Method and any claim about causes.
RMP.10:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “Mine the log and recover the Method.” | Establish the events and declarations actually recorded. Use the matrix for any unresolved question about intent, tacit work or context. |
| “Interview experts until their stories converge.” | Sample for variation relevant to the receiving question. Retain consequential disagreements, limits of recall and supported minority variants. |
| “Use every evidence form.” | Choose the sources that can establish or discriminate among the material claims at a justified cost. |
| “A specialist programme must always obtain another unseen case.” | Select a further check for a material unresolved claim. Finish on sufficient evidence or report the limit on the conclusion. If a proposed use depends on missing evidence, narrow or defer it as appropriate. |
| “The held-out case fits after we revised the account.” | Record predictions before inspection. Report departures from them and identify any post-inspection revision. A fresh prediction test requires evidence withheld from that revision. |
| “The reconstructed account is now an admitted Method.” | Report the account at its supported scope. Use A.3.1 if the work also requires Method identification. |
RMP.10:9 - Consequences
The receiver gets candidate accounts tied to the evidence for each claim. The reconstruction can preserve distinct variants or establish that the sources support only a record of local work. Either can answer a consequential question about practice.
Specialist sampling, access and analysis take effort. Even a well-conducted inquiry may establish only a local observation or a limit on what can be recovered.
RMP.10:10 - Rationale
Overt action, logged recurrence, recalled judgement, tacit coordination and variation across settings present different evidential questions. Match each consequential claim to sources that can answer it. The matrix, comparison by scope and stopping conditions make a combination inspectable where several sources are needed.
RMP.10:11 - SoTA-Echoing
| Source | Retained contribution | Use boundary |
|---|---|---|
Current FPF A.3.1.MR | Recover a provisional account from occurrences, with its sources, substantive rivals, useful distinguishing questions and limits. A narrower result can be sufficient. | Enter RMP.10 when the receiving question still needs a larger programme and its attainable contribution warrants the effort. |
| Klein, Calderwood and MacGregor, Critical Decision Method | Retrospective critical-incident probes for recalled cues, options, judgements and counterfactual reflections. | Use these for the experience and reasoning reported by the participant. Logged events, recurrence, population rates and causes each require evidence bearing on that claim. |
| IEEE Task Force, Process Mining Manifesto | Discovery, monitoring and conformance analysis over recorded event logs. | Use the semantics and coverage of the fields. Intent, tacit contribution, Method identity and causal explanation each need their own grounds. |
| Ordinary observation and artifacts | Evidence of overt occurrences and their results. | Identify what the observation or artifact covers, including its access, observation scheme and time window. |
RMP.10 combines the claim matrix, sampling for relevant variation, comparison of contradictions by scope, selection of further checks and a stopping judgement. Reconsider the combination if a source method changes an operation it supplies, or if a representative use shows that the specialist work adds too little to the account or its intended use for its cost.
RMP.10:12 - Relations
- Use RMP.2 for an open design choice, RMP.3 to develop or assess its operationalization, RMP.4 for the material actually available, and RMP.5 for an unresolved question about the inference. Use adequate supplied results directly. RMP.9 addresses a difficulty with the research Method itself.
- Use the ordinary recovery supplied by
A.3.1.MRdirectly when it answers the question. Its remaining evidential limits help define a possible specialist inquiry. A.15.1governs any claimed Work occurrence;A.10governs evidence paths and provenance;A.3.1alone governs Method identification.- C.39.RP can retain a candidate account provisionally in a repertoire and keep other material in its appropriate role. A.3.1.QM can qualify an identified Method or a candidate Method account while preserving that status.
- For later description, support, trial or architecture work, use the account and evidence within the conditions they cover. Identify the additional contribution needed for a stronger use.
- RMP.11 addresses how and why a Method architecture differentiated. Use historical sources for what changed and appropriate discriminating evidence for a proposed cause. A candidate account from RMP.10 may contribute to that inquiry.