RMP.10 - Reconstruct a Candidate Method Account from Practice Evidence

Status: Stable

Type: Method pattern

Primary working result: a claim-to-evidence dossier with scoped candidate Method accounts, contradictions and rivals, results of any selected further checks, evidence limits, and the next receiving use—or a justified lowering when the evidence supports only Work description, a local workaround, tool behavior, or an unresolved grouping.

RMP.10:0 - Use This When

Use this pattern only after A.3.1.MR has recovered an ordinary candidate account or honest lower result and a named receiving decision still cannot be made without a larger evidence programme. Typical triggers are heterogeneous settings, disputed variants, tacit cues or judgments, incomplete records, consequential use, or a need for a stronger held-out application.

Begin with the receiving decision and the few candidate-account claims whose uncertainty changes it. Select evidence forms for those claims rather than collecting every available trace or interview.

The first useful result is a claim-to-evidence matrix and sampling decision. It states what would support, contradict, split, or lower each claim and why the selected evidence form can distinguish those outcomes. This makes the specialist burden visible before the study grows.

Use the larger evidence programme only when ordinary candidate recovery is insufficient for the named decision. No observation, interview, log, or synthesis backdates a Method into past Work, promotes a log into a MethodDescription, or admits a Method without A.3.1.

RMP.10:0.1 - Working Distinctions

Evidence or result	Contribution retained here	Boundary
occurrence observation and artifacts	overt actions, results, versions, coordination, and traces for one Work occurrence	observed recurrence does not identify a Method by itself
Critical Decision Method (CDM) probe	recalled critical-incident cues, options, judgments, and counterfactual reflections	recall and interviewer effects remain visible; CDM supplies no event-log claim
event-log analysis	recorded recurrence, sequence, deviation, and conformance relative to declared log semantics	tool traces describe recorded events, not intent, tacit contribution, or a MethodDescription
contextual observation or protocol elicitation	coordination, workarounds, or otherwise inaccessible reasoning when their particular risk is named	these moves are selected separately; CDM and process-mining sources do not support them by proxy
expert synthesis	claim-to-evidence matrix, decision-relevant sampling, contradiction-by-scope rule, choice of further checks, and stopping rule	disclose the synthesis rather than attributing it to the specialist sources
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

Ordinary records show only part of practice. Logs favor tool-visible events, procedures favor intended behavior, interviews favor memorable episodes, and successful outcomes can hide competent minority variants or recovery Work. A stronger reconstruction therefore needs several evidence forms and an explicit account of which claim each supports.

More evidence is not automatically better. The programme earns its cost only when its combined result changes candidate-account content, scope, rivals, or the receiving decision beyond what A.3.1.MR already returned.

RMP.10:2 - Problem

A trace-only reconstruction turns log regularity into a Method. An interview-only reconstruction turns confident recall into recurrence. A majority-vote synthesis erases variants and failure cases. An expanding study collects material without a stopping decision.

The resulting account looks rich yet cannot say which claim each item supports, what would contradict it, or which remaining uncertainty matters to its use.

RMP.10:3 - Forces

Force	Tension
Tacit contribution	Important cues and judgments may be absent from records, while elicitation can distort them.
Heterogeneity	Several performers and settings improve discrimination, while indiscriminate sampling raises cost.
Contradiction	Variants may be real, while some disagreement is error or incomplete evidence.
Tool visibility	Event logs are precise about recorded fields, while invisible coordination and intent remain outside them.
Further discrimination	An unseen case can test prediction or transfer, while an unavailable or decision-irrelevant case adds no useful assurance. Retrofitting after inspection loses the intended discrimination.
Specialist burden	Consequential decisions may justify a programme, while ordinary recovery needs an affordable stop.

RMP.10:4 - Solution

RMP.2 supplies a selected evidence strategy or a justified stop when that design question remains open; a compatible supplied selection is enough. RMP.3 makes its consequential operational choices executable, and RMP.4 preserves the actual observation, elicitation and log trace with its access limits. The reconstruction below makes the specific claim-to-evidence connection: which uncertainty about a reusable way needs which evidence, how setting-specific variants survive contradiction, and what bounded account the combined material supports. Reuse an adequate design or trace; the programme needs the missing discrimination, not another copy of those results.

Organize evidence around decision-changing claims, keep evidence forms distinct, resolve contradiction by scope, and select further checks only where their attainable result warrants the burden. Return scoped accounts or a lower result when the receiving decision has an adequate basis.

RMP.10:4.1 - Pattern-Use Unfolding

Name the receiving decision and unresolved claims. Include only intended result, entry conditions, reusable operations or invariants, cues and decisions, participants and capabilities, information and artifacts, support, variation, recovery, and stop claims that can change the decision.
Build the claim-to-evidence matrix. For each claim, state what observation could support, contradict, split, or lower it and why the evidence form can distinguish those outcomes for that claim.
Sample for decision-relevant variation. Select cases that differ in success or failure, routine or exceptional conditions, performer, setting, and tool or provider. Add a disconfirming case when the emerging account explains only the convenient sample. Use no universal participant count.
Keep evidence forms distinct. Use occurrence observation/artifacts for overt actions and results; CDM for recalled critical-incident cognition; event-log analysis for recorded recurrence and deviation. Select contextual or protocol evidence only for a named gap and risk.
Keep occurrence and candidate layers separate. Record each Work occurrence before abstracting an account. Preserve missing fields, observer effects, recall limits, tool coverage, and source access.
Resolve contradiction by scope, not vote. Compare performer, setting, outcome, and evidence form. Correct a supported error; otherwise split variants, narrow applicability, retain rivals, or lower the claim.
Choose whether a further check is needed. Identify the unresolved claim and the possible answers that would change the receiving use. Compare the attainable discrimination with evidence access, practitioner capacity, delay, and the whole acquisition burden. Select a held-out case when prediction or transfer to that case matters and can be examined usefully. State each serious account’s predictions about cues, decisions, variation, and result before inspecting it; record surprise and revision. Another claim may instead need a source comparison, a targeted elicitation, or no additional check because the existing evidence already supports the bounded decision. An unavailable check leaves its claim uncertain; it does not oblige an unproductive study or license a stronger claim.
Stop or lower. Stop when the scoped accounts and explicit uncertainty dispositions support the receiving decision. Rivals may remain unresolved when distinguishing them would not change that decision. Narrow the use or defer it if a load-bearing uncertainty remains. Return no candidate account when the evidence supports only a Work description, local workaround, tool behavior, or unresolved grouping.

RMP.10:4.2 - Record the Result

Result position	Required content
receiving boundary	Decision, situation, consequence, candidate accounts, and unresolved claims.
claim-to-evidence matrix	Claim, discriminating observation, selected evidence form, support/contradiction/split/lowering rule, and stopping use.
sample and occurrences	Decision-relevant variation, each Work occurrence, source access, missing fields, and evidence-form limits.
synthesis	Scoped accounts, retained variants/rivals, contradiction disposition, and attribution of each synthesis move.
selected further checks, when needed	Claim and use at issue, why the attainable answer warrants the burden, actual result and remaining uncertainty. For a held-out check, also preserve predictions made before inspection, surprise and revision. When existing evidence suffices, state that basis in the return; no empty held-out record is needed.
return	Account(s) or lower result, evidence limits, next receiving use, and reopen condition.

RMP.10:4.3 - What Changes in Practice

Teams stop equating a discovered sequence or interview narrative with the Method. They spend specialist effort only where a receiving decision needs it, know which evidence form supports which claim, and can retain two scoped variants instead of averaging them into a misleading universal account.

RMP.10:5 - Archetypal Grounding

RMP.10:5.1 - Ordinary `A.3.1.MR` Stop

A maintenance team has six source-traceable calibration Work records using the same released instruction, input schema, equipment configuration, decision authority, and result meaning. One failed record contains an explicit missing-input stop already described by the candidate account. The receiving decision needs only a source-traceable account for comparing two instructions; no tacit cue, disputed variant, consequential transfer, or held-out prediction changes that decision.

A.3.1.MR returns the source-traceable candidate account, any real rival and the important gaps, with its provisional status and comparison-use limits. No distinguishing question or available follow-up is needed for this instruction comparison. RMP.10 is not entered; interviews and process mining would add cost without changing the result.

RMP.10:5.2 - Genuine Escalation: EC-417 Evidence Reconciliation

The EC-417 decision cannot determine whether internal and supplier-originated evidence reconciliation are one account or scoped variants from ordinary records alone. Here the consequential evidence-closure question, available case access and practitioner capacity justify the larger programme and its whole burden. This constructed reconstruction uses a twelve-case development sample plus one held-out case; that count is not an entry rule for other recoveries:

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	overt evidence versions, board records, integration bundles, approval states, and closure results	no population estimate or tacit-cue claim
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	log fields do not establish intent or a reusable Method
disclosed expert synthesis	twelve-plus-one sample, internal/supplier scope split, contradiction rule, held-out discriminator, and stop	not attributed to CDM or process-mining sources

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`	rig unavailability, rather than evidence origin, would trigger the hold and next-slot decision	the same branch would occur for internal and supplier changes and would clear when rig access returned

The held-out case then showed cues of supplier-owned geometry, restricted provider access, and available rig capacity; the decision allowed reversible early integration but withheld closure pending signed supplier approval; the variation required a signed-delta comparison and one affected verification; and the result was truthful closure after signed approval arrived at D-8. No load-bearing observation surprised the supplier-scoped account. The available rig contradicted the capacity-only rival for this case, and the retained supplier-approval requirement contradicted the internal-account extrapolation.

The resulting disposition is to keep C-Evidence-Reconcile-Internal for the eight internal cases, keep and narrow C-Evidence-Reconcile-Supplier to supplier-owned configuration with the signed-evidence branch, and retain rig availability as a support condition rather than the account that explains this split. The scope split is not decided by majority count. One held-out supplier case leaves transfer to other suppliers, other configuration classes, and missing-approval situations uncertain; neither account is admitted as a Method, and no effectiveness or population claim is made.

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 its mixed logs and instruction editions cannot tell whether an urgent route was a repeatable cue-based branch or an occasional supervisor override. The receiving museum archive needs a qualified comparison of the two candidate accounts for this service’s final year. It is not deciding to reopen the service or transfer either account to current work.

The larger programme is justified because the disputed cue is absent from the logs. Its claim matrix selects the dated routing sheets and targeted critical-incident interviews with the two available former dispatchers. The sheets record whether replacement stock was present; the logs record only the chosen route. Linking them to the same occurrences shows that the disputed route accompanied absent stock in the accessible cases. Each dispatcher recalls using the stock cue and describes one exception requiring supervisor involvement. Their recalled reasons remain elicited accounts; the routing sheets support recorded stock and routing, not unrecorded intentions or universal recurrence.

The evidence supports a stock-conditioned candidate branch with a separately retained supervisor exception. The archive can now compare that account with the earlier instruction and state the unresolved gaps. A new live repair cannot be observed because the service has closed. Simulating one would test present performance under new conditions, which the archive’s comparison does not need. The programme therefore returns the bounded account, source links, recall limits and unresolved coverage outside the accessible records. It makes no claim about transfer or effectiveness, and it does not identify a Method through these observations.

The programme entered RMP.10 and completed useful specialist work. Its stop rests on the adequacy of that work for the receiving comparison. If a later operator wants to reuse the reconstructed branch, that changed use reopens the evidence and check choice; the archive’s descriptive result cannot settle it.

RMP.10:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
trace bias	Recorded sequence becomes the Method or its complete description.	State log semantics and combine only with evidence needed for the claims.
interview bias	Memorable explanations become recurrence or causal evidence.	Keep CDM claims to cues, options, judgments, and reflections with recall limits.
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	Using a named evidence Method lends authority to the whole synthesis.	Attribute each sourced move and disclose the project synthesis separately.
programme bias	More cases are collected because the study is open.	Tie sampling and stop to the receiving decision and load-bearing claims.

RMP.10:7 - Conformance Checklist

A.3.1.MR has already returned an ordinary result, and a named receiving decision justifies the larger burden.
The first useful result is a claim-to-evidence matrix and decision-relevant sampling choice.
Observation/artifacts, CDM, event-log analysis, contextual/protocol evidence, and expert synthesis keep distinct contributions and limits.
Each Work occurrence is recorded before candidate-account abstraction.
Contradictions are resolved by scope or retained, not averaged by vote.
Any further check addresses a use-changing uncertainty and has an attainable result worth its burden; an adequate existing basis can support a bounded stop.
A selected held-out discriminator states predictions before inspection and records surprise/revision.
Scoped variants and rivals remain visible.
The result can lower to Work description, local workaround, tool behavior, or unresolved grouping.
No evidence form identifies a Method, creates a MethodDescription, backdates Work, or establishes causality by itself.

RMP.10:8 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Repair
“Mine the log and recover the Method.”	Recover only recorded events; use the claim matrix to identify missing intent, tacit, and context evidence.
“Interview experts until their stories converge.”	Sample for decision-relevant variation and preserve contradiction, recall limits, and minority variants.
“Use every evidence form.”	Select only forms whose possible results can change a claim or the receiving decision.
“A specialist programme must always obtain another unseen case.”	Select the check from the unresolved claim and receiving use; finish on adequate existing evidence, or narrow/defer the use when uncertainty matters.
“The held-out case fits after we revised the account.”	Record predictions before inspection and report surprise rather than retrofitting.
“The reconstructed account is now an admitted Method.”	Return the account and send Method identity to `A.3.1`.

RMP.10:9 - Consequences

For consequential decisions, practitioners reconstruct candidate accounts claim by claim, make the sources traceable, and can retain variants. The receiving decision gains stronger accounts or an honest lower result rather than a single fluent reconstruction.

The cost is specialist sampling, evidence access, and analysis. Some evidence will remain unusable for the desired claim, and a well-run programme can still return no Method candidate.

RMP.10:10 - Rationale

No single evidence form covers overt action, recorded recurrence, recalled judgment, tacit coordination, and cross-setting variation. Combining these evidence forms is useful only when each is connected to a claim and a receiving decision. The matrix, scope rule, justified check choice, and stop make that combination testable without claiming a universal research protocol.

RMP.10:11 - SoTA-Echoing

Source	Retained contribution	Use boundary
Current FPF `A.3.1.MR`	Ordinary several-occurrence recovery, real rival accounts, source-to-claim trace, useful distinguishing questions and honest lowering. A provisional account can finish without irrelevant or unavailable follow-up.	RMP.10 begins only when a named decision needs and warrants its larger programme; the ordinary question is not a study commitment.
Klein, Calderwood, and MacGregor, Critical Decision Method	Retrospective critical-incident probes for cues, options, judgments, and counterfactual reflections.	CDM supplies no event-log, recurrence, population, or causal result.
IEEE Task Force, Process Mining Manifesto	Discovery, monitoring, and conformance analysis over recorded event logs.	Event-log regularity establishes neither intent, tacit contribution, Method identity, nor causality.
Ordinary observation and artifacts	Overt occurrence evidence and result traces.	Observation supplies only what its access, scheme, and window support.

The claim matrix, decision-relevant sampling, contradiction-by-scope rule, conditional further checks, and combined stop are the bounded DPF synthesis. Reopen when a current evidence Method changes one of those moves, or when representative uses show that the extra burden does not improve account scope or the receiving decision.

RMP.10:12 - Relations

Use RMP.2 when research-design selection is still open and RMP.3 for the operationalization of a selected design; RMP.4 preserves the actual material. Use compatible supplied results directly. RMP.5 can criticize the resulting account under its actual evidence relation; RMP.9 receives a separate difficulty in the research Method itself.
A.3.1.MR supplies the ordinary floor and specialist-exit question; RMP.10 does not replace it.
A.15.1 governs any claimed Work occurrence; A.10 governs evidence paths and provenance; A.3.1 alone governs Method identification.
C.39.RP may add returned accounts provisionally to a repertoire. A.3.1.QM may qualify an account without changing its status.
Later description, support, trial, or architecture patterns consume only the scoped account, evidence limit, and next use their entry conditions admit.
RMP.11 addresses a different question: why and how a Method architecture differentiated. Use it for that explanation and any needed causal-use support assessment; evidence reconstruction here supplies no causal conclusion by itself.