Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

RMP.11 - Explain Method History with Discriminating Evidence

Status: Stable

Type: Method pattern

Primary working result: a differentiation account of a dated change in a Method, family or relation among Methods. For an explanatory question, identify the proposed links, serious rivals, diagnostic observations and degree of support. If a use requires causal reliance, give a separate C.28 causal-use support result. A present architecture decision requires its own criteria and authority.

RMP.11:0 - Use This When

Use this method to investigate how an identified Method, an independently established family or a named relation among Methods changed. You may want to know when a variant appeared, why a contribution separated, why a provider or profession retained a form, or how an environmental change affected practice. Establish what happened before deciding how well the evidence explains it.

Identify the Method, established family inclusion or relation at issue, the change and the period. Ask whether the recipient needs its chronology, evidence comparing explanations, or support for a specified causal claim. If a current decision uses that history, identify which conclusion it needs.

A first useful result may be a dated sequence with its sources and limits. For causal reliance, specify the question, claim kind, rung of the causality ladder and support required.

A local name can identify candidates for investigation. Establish professional family membership from independent evidence. If ordinary chronology answers the question, use it directly. Use RMP.11 to determine what the documented changes or competing accounts support. Popularity can help locate a diffusion question. When a present architecture choice also needs the history, assess that choice by its own criteria and authority.

RMP.11:0.1 - Working Distinctions

Name used hereMeaning
explanandumThe differentiation to explain in an identified Method, an independently established family inclusion or a named relation among Methods.
differentiation accountA dated account of the change and its evidence. For an explanatory inquiry it includes link claims, rivals, diagnostic observations, support grades, limits and conditions for reconsideration.
descriptive sequenceDated editions, evidence of Work, variants, disappearances and decision points for the period in question.
link claimA proposed connection among a pressure or change, an affected actor or carrier, a response or variation, its selection or retention, and the resulting change in a Method or its relations.
rivalA materially different account such as constraint, provider/tool availability, regulation, authority, diffusion/fashion, recording artifact, redesign, or survivorship bias. Rivals may coincide.
causal-use support resultA separate C.28 result naming the question, claim kind and rung, with references to the findings that supply the required support and to the assessment of common threats. Its verdict identifies supported and unsupported uses, limits, time window and grounds for reconsideration.
non-causal observation or hypothesisAn observation or proposed association reported at its supported scope. It may help design a bounded probe.
downstream architecture decisionA separate authorized choice with its own criteria, conditions for stopping and resource burden. Any causal premise it uses must fall within the causal-use verdict.

RMP.11:1 - Problem Frame

An account of professional Method change relates variants recorded in successive sources to changes in institutions, tools, regulation and local Work. It examines deliberate redesign, diffusion, fashion, retention and loss. Questions about variants and selection help develop competing accounts. Process-tracing research supplies methods for examining the sequence within a case, rival explanations and diagnostic observations.

Use C.28 when an inquiry or decision relies on a causal part of the historical explanation. An established sequence can support description and a hypothesis. To claim what an intervention would do, establish the required support for the interventional use.

RMP.11:2 - Problem

A pressure can precede a change for several reasons. Search frequency can measure attention, and institutional promotion can document publicity. Where the question concerns adoption, seek evidence of use. In an account of historical alternatives, look for abandoned variants that surviving editions omit. A claim of professional family membership needs grounds beyond a local grouping.

A historian can report an established change while its cause remains unresolved. If a decision needs the cause, identify and assess the evidence for that stronger claim.

RMP.11:3 - Forces

ForceTension
Useful historyA dated account can answer when a change occurred or expose an alternative that matters to a present use. Select the chronology for the historical question.
Diagnostic depthAn observation can favour one account within a case. Identification and estimation require grounds specific to the causal use.
Evolutionary languageVariation, selection, retention and loss suggest questions. Establish a proposed causal link from the relevant evidence.
Causal costDescription or a hypothesis can answer some questions. A use that depends on an effect can require substantially more work.
Present authorityHistory can inform a choice. A decision about today’s architecture also needs its own criteria and an authorized decision-maker.

RMP.11:4 - Solution

Use surviving records and their access or loss conditions from RMP.4, and an applicable corpus and account of source dependence from RMP.7 when needed. To explain differentiation, identify competing accounts, determine what observations could distinguish them, and weigh findings in light of the sources already used. A dated sequence may answer when the change happened. For causal reliance use the separate C.28 assessment.

Establish the dated changes. For an explanatory question, compare plausible accounts using observations that can distinguish them. Apply C.28 when a claim or decision calls for causal reliance, and identify the scope of each result.

RMP.11:4.1 - Pattern-Use Unfolding

  1. Bound the explanandum. Identify the Method under A.3.1, an independently established family inclusion or a named relation among Methods, and the change at issue. Use a local grouping to locate candidates. For a claim about professional membership, establish it separately.
  2. Identify the historical use. State whether the question is when the change occurred, what the evidence suggests about the reasons, or which causal claim it supports. For causal reliance, specify the CausalUseClaimKind, target CausalityLadderRung, relevant comparator or intervention and proposed links. Return a dated account when it supplies the requested result.
  3. Establish the dated sequence. Recover the source editions, Work evidence, appearances, disappearances, abandoned variants and decision points pertinent to the change. Use the resulting timeline for chronology or as an index to evidence for an explanation.
  4. Propose explanatory links where needed. Identify the pressure or environmental change, the affected actor or carrier, response or variation, selection or retention, and resulting Method or relation change. Use mechanism in the cited source’s sense unless a distinct A.6.1 U.Mechanism has been identified.
  5. Identify serious rivals. Consider demand, constraints, tool or provider availability, regulation, authority, fashion, diffusion, recording changes, deliberate redesign and survival of the records where they fit the case. State which accounts compete and which contributions could coexist.
  6. Derive diagnostic observations. What dated records, version differences, decisions, Work evidence, interviews, abandoned variants, negative cases or cross-setting contrasts would be more expected under one account than another? Use existing material or obtain additional evidence when warranted. Preserve provenance and source dependence. Before grading the link claims, compare the evidence as described in :4.4.
  7. Assess a named causal use through C.28. Identify the question, claim kind, rung, applicable evidence paths and data regimes, specialist findings, common threat screen, verdict, supported and unsupported uses, limits, evidence window and conditions for reconsideration. Use the results that actually supply the required support. An unresolved relevant threat or missing required identification, bound or estimate limits the verdict for that particular use.
  8. Return the results at their supported scope. Mark differentiation claims as observed, source-supported, inferred, expert-estimated, contradicted or missing, and retain material rivals. Identify any causal-use result separately. For a present choice, the authorized decision-maker may rely on causal conclusions within the verdict. If the verdict is unsupported or undecided, a separate non-causal observation or hypothesis may still justify considering a bounded trial.

RMP.11:4.2 - Record the Results

ResultRequired content
differentiation accountThe change and dated sequence, with source editions, Work evidence, grades and limits. For an explanation, include the proposed links, rivals and diagnostic comparisons with their assumptions and source dependencies. Identify evidence that could materially revise the result.
causal-use support result, when neededIdentify the question, claim kind and rung. Cite the findings supporting its components and the common-threat assessment. Give the verdict, the causal uses it supports or rules out, its limits and evidence window, and the changes that would warrant reconsideration.
non-causal observation or hypothesis, when neededIdentify it separately, state its descriptive grounds, any bounded use in a design, the inferences it cannot support and any changes that would warrant reconsideration.
use by a downstream decision, when applicableThe result and the reliance it supports. Authority and criteria for the decision belong to the party making it.

RMP.11:4.3 - What Changes in Practice

A dated account can recover forgotten variants and identify competing explanations. A limited causal verdict tells a decision-maker which reliance lacks support. A separate non-causal observation can still inform an authorized reversible probe.

RMP.11:4.4 - Weigh Historical Evidence between the Actual Accounts

Distinguish the reliability of a source from the diagnostic weight of its contents. A reliable fact expected equally under all serious accounts can establish the sequence while leaving their relative support unchanged. A potentially discriminating statement may carry little weight if its date, authorship or relation to the events is uncertain. Use these judgements when grading claims in :4.1.

  1. Compare the actual accounts. For the same finding, ask how expected it would be under each serious account given the evidence already used. Explain the difference. If two causes can operate together, compare their proposed contributions or consider a combined account.
  2. Examine how the finding became available. Distinguish the event from a later assertion. Ask what the source could observe, what would be recorded and how records were selected and preserved. Absence can weigh against a proposed event when that event should have left a record in the material actually examined.
  3. Identify new information and its origin. A brochure, an interview repeating it and an article citing the interview can transmit one assertion. Assess what each adds given the earlier evidence. A new source date or an independent Work observation can add information even within the same archive.
  4. Return a conditional comparison. State which findings favour which accounts and under what assumptions. Report unresolved rivals when the relevant observations are equally expected or source uncertainty defeats discrimination. Examine whether the preference survives plausible changes in coding, selection, dependence or weight of a finding. If it does not, describe that sensitivity. If the question needs a numerical comparison and the observation model and assumptions warrant it, use a quantitative analysis.
  5. Reconsider earlier findings when the account changes. A new actor, date or proposed mechanism can change what earlier evidence implies. Compare the revised account with the relevant prior corpus and the new item, accounting for dependence.
  6. Identify the use the evidence supports. A comparison can yield a scoped historical hypothesis or identify a worthwhile further inquiry. For causal reliance, supply the relevant findings and limits to C.28. If a revised premise mattered to an existing repertoire or decision, trace that reliance in C.39.RP, A.3.1.QM or C.32.MWA.PP. A current Method can retain a qualification that rests on independent evidence.

RMP.11:5 - Archetypal Grounding

RMP.11:5.1 - Descriptive Stop

Suppose a design office needs to reconcile names and source editions after drawing signoff differentiated. For this example, A.3.1 identification and A.3.1.MV variant qualification already establish M-Signoff-0 and local variants M-Signoff-E and M-Signoff-M. All return approve or reject for a drawing. The electrical variant requires clearance and harness-revision checks, the mechanical variant load-case and fit checks. Each withholds approval when its required check is absent. These are independently established differences in the local Methods. The question here concerns the timing of their documentation and use.

The office needs to establish when the different checks were approved and used in the surviving records, and when separate electronic forms represented them. Dated instructions and Work records can answer those questions even if the first-ever use is unknown.

The case also identifies ElectricalReviewer-E and MechanicalReviewer-M as Agents for the respective checks under A.13, and their 9 and 18 April occurrences WE7 and WM4 as Work under A.15.1. They enacted M-Signoff-E and M-Signoff-M using the respective E1 and M1 instructions. The following records form the source set.

Date and sourceRecoverable fact and limit
15 January 2024, signoff instruction S3A common instruction covers both drawing types and requires the presence of evidence. Neither local variant’s distinct test-and-withhold rule appears in S3. Whether somebody used either check earlier remains open.
4 March, exception log X2, and 11 March, proposal P1X2 records two returned drawings, one lacking electrical-clearance evidence and one lacking the mechanical load case. P1 cites these exceptions, proposes the two domain-specific rules and retains common signoff with expert escalation as an alternative. This establishes a stated reason for the proposal.
2 April, approval A14 and instructions E1/M1A14 approves the two local variants for the respective drawings. E1 and M1 specify different checks and returns for failure. A14 leaves the common-with-escalation proposal unselected. The deliberation minutes are missing.
9 and 18 April, signoff Work WE7/WM4 and their annotated resultsIn WE7, ElectricalReviewer-E followed E1 and withheld approval for missing clearance evidence. In WM4, MechanicalReviewer-M followed M1 and withheld it for a missing load case. These records establish two enactments before the forms separated. Earlier occurrences and the extent of uptake remain open.
6 May, PLM migration note T2 and form edition F2F2 introduces separate electronic forms and names for approval records. T2 states that they carry the E1/M1 rules already in use. The change documented here concerns how those rules are represented.

Before examining the April records, the office considers two accounts. R-demand attributes the proposal and selection to domain-specific omissions. It predicts a problem record, a response proposal and distinct checks before migration. R-carrier attributes the apparent split to the May change in recording or naming. It predicts unchanged checks under the new forms. The March returns and proposal make R-demand plausible. The searchable PLM history begins with F2, which makes a recording change plausible until the earlier instructions and Work are examined.

E1/M1 specify distinct checks and WE7/WM4 record their enactment in April, before F2. That contradicts the strong R-carrier claim of a naming-only change in May. The records fit R-demand. They leave open why the office chose separate rules over common signoff with escalation and what other pressures contributed. The deliberations are missing. A within-case inquiry might investigate the missing link through further sources. A possible contribution of the carrier to later retention also remains open.

DA-Signoff-Differentiation-1 returns these grades and limits:

ClaimGrade and allowed use
The common and domain-specific instructions differ in the named required checks and stops.Source-supported by S3/E1/M1; Method identity and variant qualification remain the separate case premises.
Separate rules were approved by 2 April and enacted in the named April occurrences.Source-supported by A14 and WE7/WM4. The dates bound the documented approval and two uses. The first-ever use and extent of uptake remain open.
The March exceptions were a stated reason for proposing the variants.Source-supported by P1. The effect of those exceptions on selection needs its own evidence.
The split was merely a May renaming with no earlier semantic difference.Contradicted by the April instructions and Work records.
Demand caused selection over common signoff with escalation, or the carrier contributed to later retention.Missing causal support for these links. The deliberation evidence and evidence of later continuation are incomplete.

In DA-Signoff-Differentiation-1, retain S3 as the common predecessor account, E1 and M1 as different variant descriptions and F2 as their later forms. The dates and observed signoffs answer the reconciliation question. The first occurrences and reasons for selection remain unresolved. An earlier instruction, a deliberation record or contrary Work evidence could revise the relevant claim. A request to choose a present architecture would introduce a different decision.

RMP.11:5.2 - Causal-Use Branch and Non-Causal C.32.MWA.PP Consumption

Suppose a team considers release alternative B2 from C.32.MWA.PP:5.3 for EC-417. B2 starts integration from a specified provisional supplier-evidence edition and reconciles it with signed evidence at the safety-closure checkpoint thirteen days later. Supplier preparation shares the reconciliation workload. Signed evidence, separate safety and release decisions, and the provisional evidence history are required. The supplying comparison gives capacity, confidentiality, assignments, permissions, recovery and trial-entry conditions. Here the question concerns the possible relationship of checkpoint timing to later reopenings. The four results below serve different uses.

  • DA-EC417-CadenceDifferentiation-1 records the observed co-occurrences. The dates, variants and selection history needed for a full differentiation account remain incomplete.
  • CUR-EC417-CadenceEffect-1 is the causal-use support result;
  • DC-EC417-CadenceMismatch-1 is a non-causal timing/co-occurrence hypothesis; and
  • AD-EC417-B2-Trial-1 is the receiving C.32.MWA.PP architecture decision.

The question in CUQ-EC417-CadenceEffect-1 is whether starting provisional-evidence reconciliation in the early integration slot would reduce mismatch-related reopenings compared with starting at the signed-evidence checkpoint thirteen days later, for EC-417-like releases under the stated team, supplier and change class. Its causalUseClaimKind is causalEffectClaim and the target rung is interventionalActionRung.

The support components are evidencePathRefs=[EP-EC417-BundleSequence-20, EP-EC417-RigAvailability-20, EP-EC417-QuarterlyCadence-2] and empiricalDataRegimeRefs=[EDR-EC417-NaturalReleaseHistory]. Identification and an estimate for the named effect are missing.

Common threat screen CTS-EC417-CadenceEffect-1 records:

Threat-screen fieldResult
causalUseQuestionRefCUQ-EC417-CadenceEffect-1
interventionWellDefinedOrConsistencyliveThreat
temporalOrderingclear
exchangeabilityOrConfoundingliveThreat
positivityOrOverlapliveThreat
interferenceOrSpilloverliveThreat
selectionCensoringOrMissingnessliveThreat
measurementErrorOrConstructShiftliveThreat
transportToTargetliveThreat
routedThreatRefs[]
resultingSupportBoundaryunsupported

The screen leaves the named threats unresolved, and the C.28 verdict is unsupported. The supportedUse is to flag the limit on interventional reliance. The unsupportedUse includes attributing the reopenings to cadence mismatch and claiming B2 will reduce them. The evidence window covers the named twenty releases and two earlier cases for this team, supplier and change class. Reconsider the verdict if a governed comparison, replayable identification or supported bound distinguishes reconciliation timing while controlling or explicitly modelling rig availability, approver capacity, outcome definition and evidence access.

DC-EC417-CadenceMismatch-1 retains the observed timing and co-occurrence as a trial hypothesis and design constraint. With evidence of capacity, confidentiality, authority and reversibility, AD-EC417-B2-Trial-1 selects a bounded B2 trial. SafetyReviewer-17 performs W-SafetyEvidenceDecision-17 under ASG-SafetyReview-17 and AUTH-SafetyEvidence-17 for the evidence condition. ReleaseDecider-17 performs W-ReleaseDecision-17 separately under ASG-ReleaseDecision-17 and AUTH-ReleaseDecision-17 for branch entry and release disposition. The causal verdict marks a limit on the decision’s interpretation.

RMP.11:5.3 - A Dated Proposal Has More Weight than Repeated Promotion

Extend the constructed signoff history from :5.1, keeping the independently identified Method and variants. H-response says repeated domain-specific omissions contributed to selecting separate rules. H-tool-only says a provider’s form package induced the split and the omissions were cited afterward. Compare their support. Tool support may also have helped retain rules initially selected for other reasons.

An authenticated internal memo dated March compares separate rules with common escalation. It recommends separation because the named specialist would be unavailable. Its date precedes the earliest documented provider contact. A problem-specific recommendation at that point is more expected under H-response than H-tool-only. Its weight depends on the memo’s authenticity and role in the decision, and on the possibility of earlier provider influence outside the recovered records.

A budget approval cites the memo and establishes that resources were authorized. Its repeated rationale adds no independent account of the reason. A later brochure and three interviews repeat the launch narrative, showing that it circulated. Trial records were not routinely preserved. Even a well-documented trial might therefore leave no surviving record. Failure to find one adds little evidence against a trial.

Under these assumptions, H-response receives more support than H-tool-only. Provider influence and a mixed account remain plausible. That relative comparison can finish the historical inquiry. If the remaining question warrants more work, records of earlier contact and of the actual decision could distinguish the accounts further. A numerical probability or an effect of imposing the rules today would require evidence and assumptions for that use.

Now suppose an authenticated February provider proposal comes to light. The March memo is no longer earlier than all known provider opportunities. Reassess the memo and budget under the revised chronology, comparing a mixed account with tool-only influence and response to omissions. The memo still establishes its stated reason. Reassess a current repertoire or decision where it relied on the changed attribution. Retain the independently supported qualification of a local variant.

RMP.11:6 - Bias-Annotation

Recurring biasLikely driftRepair
chronology biasEarlier and later events are described as cause and effect.Establish the dated sequence. Assess explanatory links and use C.28 for a named causal use when one is at issue.
survival biasThe surviving materials omit abandoned or excluded variants.Consider sources that could reveal those variants and state any consequential limits on coverage.
fashion-metric biasPublication counts, search frequency or promotion are taken as direct measures of adoption or effectiveness.Establish which attention or diffusion claim the indicator supports and what else could account for it.
family-label biasA local grouping becomes a professional family explanandum.Require independent family membership or explain named Methods and relations instead.
history-authority biasA historical explanation is used as authority to implement a change.For a current architecture decision, identify its criteria, authority, causal premises and conditions for stopping a trial where applicable.

RMP.11:7 - Conformance Checklist

  • The explanandum is an identified Method, established family inclusion, or named Method relation change.
  • The historical question and required scope of description, explanatory comparison or causal reliance are clear.
  • The dated sequence preserves the source editions, Work evidence, variants, appearances, disappearances and decisions on which the account relies.
  • Each proposed explanatory link identifies the relevant change or pressure, affected actor or carrier, response, selection or retention, and resulting change to a Method or relation.
  • For an explanatory comparison, serious rivals and their expected observations guide the use or selection of evidence.
  • Diagnostic weight reflects what each rival predicts given the existing evidence, how the sources arose and whether they repeat an earlier assertion.
  • Differentiation claims carry grades and limits, and changed accounts prompt reconsideration of the relevant earlier evidence.
  • Any causal-use result contains the complete current C.28 identity, support, threat, verdict, use, window, and reopen fields.
  • The causal-use result identifies which evidence or specialist findings support each component it relies on.
  • The historical account, any causal-use verdict or non-causal hypothesis, and any subsequent architecture decision have identifiable grounds and scope.
  • An unsupported or undecided result supplies no positive causal premise.

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

Anti-patternRepair
“The pressure came first, so it caused the Method change.”Establish what the dated sequence supports. For the proposed explanation compare link claims and rivals using diagnostic observations. Apply C.28 when the receiving use requires causal support.
“The timeline is the explanation.”Use the timeline for the chronology. For a question about reasons, compare the expected evidence under the proposed links and their rivals.
“Process tracing proves the causal effect.”Use process tracing for within-case diagnosis. For a causal use, apply C.28 and limit the verdict where required identification, a bound or an estimate is missing.
“Unsupported means the history is useless.”Return the established sequence. If a distinct non-causal hypothesis is supported or useful to investigate, state it within its scope.
“The history tells us what to implement.”Use the historical conclusion within its scope. Refer a current implementation choice to the party with the relevant authority when such a choice is needed.

RMP.11:9 - Consequences

The historical account can establish when a Method changed and restore forgotten variants. Evidence can favour some explanations over others or leave rivals unresolved. In a current decision, an authorized reversible probe may be justified from non-causal observations even when the proposed effect lacks support.

Comparing explanations requires source criticism. Assessing a causal use also requires examining the relevant threats. The best supported answer can be a dated account, a partial explanation or a stated limit on causal reliance.

RMP.11:10 - Rationale

A dated sequence, support for a causal explanation and authority for a present choice have different grounds. A chronology can be established while attribution remains open. A non-causal observation can still identify a design constraint.

Variation, transmission, fashion, retention and loss can suggest hypotheses about Method change. Compare the observations each hypothesis predicts using process-tracing methods. Apply C.28 to identify the evidence required for a causal use, including identification or estimation when that particular question calls for it.

RMP.11:11 - SoTA-Echoing

SourceRetained contributionUse boundary
Stacey et al., Methods as a form of engineering knowledgeMethod knowledge, variation and loss in engineering contexts.Use the conceptual history to frame a question. Specific causal attribution and authority for a current choice have their own grounds.
Collier, Understanding Process Tracing, with 2019 addendumThe 2011 treatment supplies within-case sequencing and diagnostic observations. The addendum develops relations among rivals and examines the limits of rigid necessity/sufficiency test classes.Use this historical foundation with later work on inference and C.28 when a causal use is at issue.
Fairfield and Charman, Explicit Bayesian Analysis for Process Tracing and A Dialogue with the DataCompare specified alternatives conditional on prior evidence, account for source dependence and reconsider existing evidence as hypotheses change.These operations support qualitative comparison. Numerical probabilities require their own justified assumptions. Judge causal support and a present architecture choice separately.
Fully specified Bayes factors for hypothesis testing and sensitivity analysis in process tracing, v2, 2026 preprintModel-based evidence weights and sensitivity analysis can show how coding, selection and weighting affect a conclusion.The binomial observation model and comparisons to one rival require substantive justification. Clustered dependence among sources limits the guarantees. Use the numerical procedure where these conditions fit.
Mahoney, The Logic of Process Tracing TestsLogic of weak, necessary-condition and strongly discriminating tests.Use the test logic to assess particular observations, then compare the support for the links across the chain.
Current FPF C.28The causal-use question, rung, support components, common threat screen, verdict, permissible reliance, limits and conditions for reconsideration.Use the verdict within its specified scope. A downstream decision also requires its own criteria and authority.

Reconsider the historical or causal account when a relied-on source changes the diagnostic comparison, an observed case exposes a consequential gap between historical and causal claims, or an intended use needs evidence the present account does not supply.

RMP.11:12 - Relations

  • Use RMP.4 for source relations and limits and RMP.7 for a corpus that accounts for dependent reports. RMP.5 can examine the inference from historical evidence. RMP.8 helps revise a changed knowledge claim and trace the uses that rely on it.
  • Use A.3.1 for Method identity and G.5 for an established family or selector claim. A local name may help locate the candidates to examine.
  • Use A.10 for sources and evidence paths. When a relied-on premise changes materially, correct a known use directly if that resolves the issue. Use A.10.1 when locating other affected uses or requalifying dependent claims together is needed. C.27 addresses temporal claims, and C.28 and C.28.CM causal support and the construction of a causal inquiry.
  • C.39.RP can retain variants and lineages with the historical and causal support appropriate to each claim.
  • C.32.MWA.PP can use the differentiation account, a causal-use verdict or a separately identified non-causal observation within its scope. The authority for the architecture choice belongs to its decision-maker.
  • Cultural continuation and professional-history questions can have their own supported answers. Use those answers for a project decision where they bear on that decision.

RMP.11:End

Referenced in the corpus

25 literal mentions in other sections. Read their context to establish the relation.