A.3.1.MI - Introduce a Method into Practice and Decide What to Keep or Change

Type: Method pattern Status: Stable

Primary working result: a bounded decision about what to keep or change after introducing a Method or examining a proposed way in real practice. Explain what was attempted, what was performed, what later use showed, and how that evidence changes the target, its introduction or the conditions of use. Preserve uncertainty where no decision is yet supported, with the next useful observation or stop.

A.3.1.MI:0 - Use This When

Use this pattern when a Method or a sufficiently interpretable proposal can be tried in real practice and the next decision depends on what its introduction and later use actually reveal. The target can remain a proposal: preserve that status and distinguish it from the independently admitted Methods actually enacted in the attempt. Start with the receiving result and the decision the observations could change.

For an ordinary first use, explain what the team tried to establish, what it did, what was later observed or could not begin, and what to keep, revise, branch, replace or stop. Separate a change to the target way from a change to how people obtain, learn or use it. The Harbor application (IS.Application:1.3) shows this small account leading directly to a receiving action.

Add the precise subjects, relations and evidence needed by the claims on which that decision relies. Sections 4.1–4.2 keep those conditions available: a capability claim needs its holder and grounds; a change needs its actual authority; a causal explanation needs C.28. A description, plan, completed introduction and successful later use remain different results. Introduction can finish while access, fitness or later performance still fails.

Use an adequate current capability without prescribing development. Bring in E.23.CDI or the relevant domain capability-development Method when the attempt requires that change; an absent result returns to that supplier or prevents the dependent attempt. A.3.1.MI does not itself produce or certify capability development. Use C.36.MC when the primary question concerns transmission, recognition, selection, retention, loss or another cultural result across a population.

A.3.1.MI:0.1 - Working Distinctions

Use the detailed positions in §4.2 when the decision needs their precise kind, identity or evidence; they are not a requirement to populate every position for every introduction.

A.3.1.MI:1 - Problem Frame

A new procedure arrives with instruction, expert assistance, a tool, changed duties, management attention and a different review occasion. Later results are credited to “the Method”, while failure is blamed on resistance or ability. Either attribution can hide the contribution that actually needs changing.

The practitioner needs to decide what to do next: retain a useful way, repair its explanation or provision, develop a needed capability, adapt the introduction, replace the target or stop. Follow the intended change through the attempt and later receiving work. Keep observations and explanations separate until the required grounds are available; otherwise an access failure can provoke redundant training, or a completed workshop can be mistaken for usable practice.

A.3.1.MI:2 - Problem

A rollout plan can be reported as adoption. Training can be reported as capability. Tool availability can be reported as use. A manager’s sponsorship can be reported as permission or authority. Later Work can be merged with the introduction Work, and a favourable domain result can be assigned to the Method without an alternative or contribution basis.

When several positions are compressed into one intervention label, the team cannot revise locally. It either repeats the whole programme or rejects it, even when the defect lies in one description, support relation, capability condition, assignment, permission, authority boundary, or outside-result assumption.

A.3.1.MI:3 - Forces

A.3.1.MI:4 - Solution

Prepare and perform a bounded introduction, observe its later use, and decide what to keep or change. Distinguish the target from how it is introduced and supplied. Begin with the small working account in §0; make each relied-on claim precise through the applicable steps below. Use C.28 only for causal reliance, and return a correction or alternative to the particular maintained result or receiving work it changes.

A.3.1.MI:4.1 - Pattern-Use Unfolding

1. Name the receiving result and decision. State what the practice should obtain, where and when the attempt and later observation can occur, and what keep, revise, branch, replace or stop would change. Preserve whether the target is an admitted Method or a candidate account. Identify the relevant population and qualification window; a company or team label alone does not establish an organizational System or selected structure.

2. Distinguish the target from its introduction. Explain the intended target change and the way of obtaining it. Where their kind or identity affects the decision, identify the claimed subjects: admitted Methods; A.3.2-classified MethodDescriptions or other claim-bearing epistemes; representations; Systems; capability bearers and results; particular Work occurrences; domain entities; organizational Systems or selected structures. Keep candidate target accounts and descriptions separate; a mixed list does not establish the claimed objects or relations.

   If A.3.1 has admitted the introduction Method, name it and identify a U.MethodDescription only when A.3.2 classifies an episteme whose one EntityOfConcern is that Method. Otherwise retain a candidate introduction account and identify its claim-bearing material as a candidate account, description episteme, or other named episteme with status, claims, and maintained result; do not classify it as U.MethodDescription. Identify any WorkPlan separately; neither the plan nor performed Work admits or enacts the candidate.

   For every relied-on assignment, permission, authority, access, use, enactment, or other direct relation, name the predicate, participant meanings, participants, and obtaining basis. Omit unclaimed positions.

3. Connect the observation to the result it can change. For each relied-on target or strategy claim and selected observation, recover the particular maintained claim or edition, its status and grounds, the observation that could support or defeat it, and the next receiving action or stop. Keep the source and qualification window where they affect use. Name the receiving Agent or governing pattern when current; otherwise retain an honest local decision rather than inventing a recipient.

4. Select the capability branch. Omit capability detail that cannot change the attempt, interpretation, or decision. When the decision does rely on capability, recover the A.2.2 basis: holder, Work family, envelope, measures, qualification window, evidence, and currentness. If existing capability is adequate and no relevant capability change is required or asserted, retain it as a reliance or observation condition; no development result is needed. A missing capability basis returns that A.2.2 question, not an automatic development prescription. Only when a capability-change claim is needed, consume a compatible E.23.CDI or domain development result naming holder, Work family, baseline, target, intervention, representative transfer Work, evidence, and currentness. If that required result is missing or stale, name the gap and the next governing development decision or stop; A.3.1.MI does not fill it.

5. Bound authorization and protected conditions. Identify the change decision-making Agent, A.13 basis, and the named assignment, permission, or authority predicate with participants and scope that permits each intended change. Name participating Systems, confidentiality and safety stops, and protected conditions. Expertise, sponsorship, project position, ownership, tool control, assignment, permission, and authority are not interchangeable bases.

6. Plan decision-relevant observations before intervention. Select only positions that can change the decision: acceptability or rejection; appropriateness or fit; feasibility; enactment or fidelity; burden or cost; reach; sustainment; changes to named targets or to the introduction strategy; and the outside result. Keep acceptability as a stakeholder observation, formal fit or transfer with A.3.1.FT, actual enactment with A.15.1, bounded reach as observed participation, and a population-level continuation question with C.36.MC. Preserve A.3.1.WT trial, A.3.1.FT fit, and C.11.MV worth questions as distinct inputs or later uses. Use §4.5 when selecting these observations requires distinguishing delivery, mechanism, adaptation and context explanations.

7. Plan separate target and introduction-strategy adaptation records. First classify every planned or observed modification as a change to the Method-related target or a change to the way it is introduced. Record what changed, when, planned or reactive status, deciding Agent and named authorization predicate, affected level, reason and conditions.

   For a target change, name the affected Method semantics, description, support, capability input, fit claim, cultural question, or local-use condition. For an introduction-strategy change, name the admitted introduction Method or candidate introduction account, its admissibly classified description episteme, and any separate WorkPlan claim. An adaptation does not by itself change the kind or status of an account, description, plan, Method or Work.

   Return each modification to its own maintained result or local stop: A.3.1.MV for admitted Method semantics or candidate lineage; A.3.2.DE for a MethodDescription correction or improved candidate-account content, retaining the applicable subject and status; another named episteme or a local A.3.1.MI stop for other content; A.15.8.MS for support; A.15.2 for a WorkPlan; A.3.1.FT for fit; or C.36.MC for a population cultural question.

8. Perform and admit introduction Work. Recover actual performers and A.13 bases, the independently admitted Method enacted by the introduction Work, action history, temporal extent, containing System, named changed subjects, used Systems, and relied-on relation occurrences. Record the result as an attempt intended to establish named conditions. A completed failed attempt remains Work even if access, usability, or later enactment did not result. A candidate introduction Method is not enacted; name only the admitted constituent Methods actually followed.

9. Observe later actual Work, failed entry, and non-use. Admit later Work independently. Record which admitted Method was enacted, or preserve candidate status and name only separately admitted constituent Methods. Also record failed entry, rejection, non-use, workaround, adaptation, support demand, and burden when observed; absence of a record is not automatically non-use.

10. Compare every selected position. For each target, introduction-strategy object, and decision-relevant observation, state supported change, no change, uncertainty, inapplicability, or missing evidence. State the particular maintained claim or edition and next action. If a continuing subject is claimed to have changed, use A.3.4; a before/after table or performed Work alone does not establish that transformation.

11. Use C.28 for causal reliance. Return observations or association at their supported strength, with the limit needed by the receiving decision. When that decision relies on a causal or contribution claim, use current C.28 for the bounded causal-use question, supported use, unsupported stronger use, population and conditions, validity threat and reopen trigger. Name a contribution relation or compound claim only with its predicate, participants, applicability, and obtaining basis. C.28 settles causal support; A.3.1.MI still makes the bounded revision decision.

12. Decide and return observations. Return keep, revise, branch, replace, stop, or a retained set with its limitation and any supported present course. Select a further observation or probe through C.11.DUA only when its obtainable result could change the decision enough to warrant its full burden and the needed window, access and authority are available. Use A.3.2.DE when the observation requires correcting a MethodDescription or candidate Method account. Its candidate branch returns improved content with unresolved identification conditions retained. Other description content returns to its own episteme or a local stop. Send other observations to A.3.1.MV, A.15.8.MS, A.15.2, A.3.1.FT, C.36.MC, a named capability-development result, another admissible maintained result, or a receiving Agent only when the particular claim or edition and next action are stated; otherwise keep the observation as a local decision or stop.

13. State non-use and refresh. The result establishes neither organization-wide adoption, cultural selection or retention, general effectiveness, causal superiority, nor authorization for another setting. Reopen when the setting, population, target, introduction-strategy or description status, separate WorkPlan, capability and support conditions, named authorization basis, alternative, outside result, evidence window, or maintained claim changes.

A.3.1.MI:4.2 - Record the Result

Keep the smallest account that lets the receiver make the bounded decision. The ordinary account in §0 and the Harbor application can suffice. The positions below expand that account when its claims require them; use the applicable content, not a compulsory inventory of unrelated objects. In particular, preserve candidate status and the admission conditions of any claimed Method or Work. Observation alone does not upgrade those claims.

A.3.1.MI:4.3 - What Changes in Practice

Teams stop reporting that a Method was “rolled out” and start distinguishing the Method-related target, the introduction strategy and its status, its description, any separate WorkPlan, performed introduction Work, later Work, named relied-on relations, and separate observations. An introduction attempt can be completed without establishing the intended conditions. A favourable outside result can remain useful without filling every observation position or becoming causal proof.

Revision becomes local. A stale target description, unsuitable target variant, failed support relation, missing capability result, weak introduction strategy, stale strategy description, unworkable WorkPlan, or local-use adaptation can be reconsidered through its own maintained claim or edition without repeating or rejecting the entire programme.

A.3.1.MI:4.4 - Minimal Constructed Introduction Replay

Calibration-Team-B wants to reduce mixed-unit release escapes. It selects admitted target Method M-Unit-Review-1 from A.3.1.MV for a D30–D60 bounded attempt; candidate target C-M-Unit-Review-Approx-1 remains outside. The changed target subjects are MethodDescription edition 4, its repaired representation, verified conversion-table System ConversionTable-B, and the assigned pre-release review Work. Separate claim-bearing results state the intended local selection and support conditions. No new organizational System or selected structure is inferred from the team label.

The introduction strategy is separately admitted Method M-Introduce-Unit-Review-1: configure the description and representation, establish and check table access, brief the reviewer on the changed distinctions, and observe one review. MethodDescription-Intro-B-1 has that admitted Method as its one EntityOfConcern, and A.3.2 classifies it as a U.MethodDescription; WorkPlan-Intro-B-1 separately schedules this bounded use. Neither episteme is the target Method or the later review Work.

CDI-R22-1 names holder Reviewer-22, calibration-report-review Work, the mixed-unit report envelope, baseline detection results, target four-of-four seeded unit cases, supervised practice and representative transfer Work, qualification evidence, and currentness through D60. A.3.1.MI consumes this result; it neither treats attendance as capability nor performs the development.

MethodEngineer-B is independently admitted as an Agent for local Method-configuration Work. Assignment occurrence ASG-Intro-B-1(MethodEngineer-B, W-Intro-B-1) covers only D30–D60. Permission occurrence PERM-Intro-B-1(MethodEngineer-B, configure, MethodDescription-4, Representation-4, ConversionTable-B) permits the three named configuration actions. Release authority remains with ReleaseDecider-B; neither assignment nor permission transfers it to the reviewer, engineer, or tool.

Authorized W-Intro-B-1 is admitted as Work performed by MethodEngineer-B inside containing System Calibration-Team-B; it enacts M-Introduce-Unit-Review-1, configures the selected target description and representation, establishes access to ConversionTable-B, briefs the reviewer, and records the assignment and authority boundary. The Work is intended to establish those local conditions. If access configuration fails, the introduction Work still occurred but the support condition did not obtain. If the briefing or sequence proves unusable while the target Method remains adequate, the affected result belongs to M-Introduce-Unit-Review-1, MethodDescription-Intro-B-1, or WorkPlan-Intro-B-1, not to M-Unit-Review-1.

Later W-B-Review-1 is independently admitted as Work performed by Reviewer-22; it enacts M-Unit-Review-1, detects a seeded Celsius/Kelvin mismatch, stops the release recommendation, and records fourteen minutes and one lookup. The observation positions remain separate: the reviewer accepts the local use; appropriateness is supported only for the named report family; table access and completion show bounded feasibility; the recorded operations support enactment for this Work occurrence; fourteen minutes and one lookup are burden observations; reach is one holder and one Work occurrence; sustainment is unknown; and one corrected report is the outside result. No adaptation occurred in this replay.

Return keep for the D30–D60 attempt on the observed local conditions, later Work, mismatch detection and corrected report. The result supports that bounded continuation. A later claim that either Method caused fewer release escapes needs C.28 and the evidence for that stronger use.

If table access failed, return the contradicted A.15.8.MS support claim and next support action. If the introduction sequence or briefing failed, return the observation to the maintained claim in M-Introduce-Unit-Review-1, MethodDescription-Intro-B-1, or WorkPlan-Intro-B-1 and keep the target result separate. If CDI-R22-1 expired, name that result and stop pending its governing development decision; if later Work changed reusable target or introduction semantics, reopen A.3.1.MV for the affected Method.

If the failed lookup path has two proposed later repairs that the available evidence cannot distinguish, and no useful comparative observation is obtainable before the current decision, return both options with that limit and keep the failed support route stopped. Return the contradicted support claim and options to A.15.8.MS. This completes the current introduction result; further comparison is selected when its obtainable answer warrants the full burden.

In a separate constructed no-development case, the same admitted review Method is introduced to Reviewer-23 by repairing the conversion-table lookup path. The current A.2.2 basis CAP-R23-1 identifies that holder, calibration-report-review Work, the mixed-unit envelope, the required detection measure, representative evidence, and a qualification window covering the attempt. It supports adequate existing capability; no capability change is required or claimed. The engineer repairs and checks the lookup path under separately supported configuration permission, and the independently admitted later review Work uses it successfully. Return keep for this bounded support change and preserve CAP-R23-1 as a reliance condition. No CDI result is missing merely because none was supplied, and no training is commissioned. If the capability basis later expires, return its currentness question to A.2.2; if the Work envelope instead changes so that development is needed, open that separately governed question. This case changes neither the reliance on CDI-R22-1 nor its expiry stop in the preceding case.

A.3.1.MI:4.5 - Explain a changed result before selecting an adaptation

Use this continuation when an unexpected result, changed setting or proposed adaptation leaves materially different explanations that would change the next application. Existing observations and a supported local correction may already settle the decision; a new study is not required merely because some causal uncertainty remains.

1. Recover how the proposed contribution is expected to work. Connect the needed result to the function each relevant contribution serves, the concrete actions or form that supply it, and the conditions under which the proposed mechanism could operate. Read the target and the introduction strategy separately. For example, a rehearsal may be intended to develop recognition of a stop condition, whereas an expert checking the completed result may supply that recognition directly. Use C.28.CM and the relevant subject practice to construct or challenge this explanation. Keep assumptions and unknown functions visible. Preserving a function does not by itself preserve Method identity.

2. Derive observations that could distinguish the live explanations. Compare what should be seen if the relevant contribution was not delivered, was delivered but did not activate the proposed mechanism, operated differently in this context, or was supplemented by another contribution. Several explanations may hold together. Link observations of actual actions, the proposed intermediate change and the outside result for the same cases and relevant times. Include failed entry and cases where the result differs. A procedure-completion count alone cannot decide among these explanations. Assess fidelity only against an interpretable baseline and only when that comparison can change the decision; unknown essential functions or an intentionally flexible strategy may support a narrower account of what was done instead.

3. Select an attainable comparison. First ask whether existing evidence distinguishes enough for the receiving action. If a further inquiry is worthwhile, construct or obtain a design tied to the competing explanations, expected observations, case differences, timing, available access and whole burden. It must explain which attainable contrast can distinguish the accounts, what remains unresolved, and how the material can be obtained and interpreted under the permitted conditions. Give the selected design, its limits and the required operational protocol to the A.3.1.WT trial or other applicable inquiry. When that construction exceeds the trial Method, obtain the missing research contribution through A.15.9; the subject inquiry retains its own Method, qualifications and authority. Check separately whether the proposed application can be performed and whether the evaluation can obtain an interpretable answer. Specify which changes the design permits: holding a configuration stable and studying an adapting configuration answer different questions. If no useful comparison is attainable, return the supported course or unresolved alternatives with the limitation that matters now.

4. Combine observations through the explanation. Use the selected methods to recover what was delivered, how participants used or responded to it, the pertinent context and the resulting benefit, harm or burden. Where broad records show a pattern, selected observations or interviews can investigate the difference; where a particular account suggests a mechanism, look for its expected consequences in the relevant records. Repeated observation can reveal a changed contribution or context. Keep the same cases, periods and measurement meanings recoverable when combining results. Separate an observation, a participant’s explanation and the investigator’s inference; use C.28 for any resulting causal reliance.

5. Make each adaptation interpretable. Compare the actual change with its prior target or introduction-strategy baseline. Recover the affected action or component, proposed function, reason, decision-maker and authorization, conditions, decision time and actual implementation time when their difference matters. Keep coupled changes together when their contributions cannot be separated. Determine what supports a claim that the function was retained, changed or remains unknown. An adaptation description supplies neither that functional conclusion nor an effect estimate. Return changed reusable operations or conditions to A.3.1.MV even if the intended function stays the same.

6. Return what the evidence changes. A.3.1.FT receives the conditions and configuration actually examined; C.11.MV receives comparable consequences, support demand and displaced work; A.3.1.MV receives the semantic change with separately qualified function and evidence; A.3.1.MI receives the basis to retain, refine, branch, replace or stop the target, its introduction, or their support. A favourable result despite poor delivery may support investigating another contribution; it neither confirms the proposed mechanism nor makes all useful work a failure. A new supported explanation or useful alternative may warrant development without contradicting the earlier bounded account. Revisit uses whose relied-on premises change through their governing patterns. Use F.0.2.RC when the change affects a source-coverage or reconstruction claim.

The result is an explanation sufficient for the named next action, with its evidence and unresolved alternatives. It can be a bounded continuation, a changed introduction strategy, a proposed target variant, a useful refinement of the explanation, or a stop. Additional detail is selected for the decision it can change.

A.3.1.MI:5 - Archetypal Grounding - Workplace Introduction and Revision

The SSFD programme reports a three-year intervention involving more than 300 engineers, training followed by supported four-to-six-month workplace projects, expert assistance, 72 reports recording SSFD use, and 41 reports supporting deeper analysis. Use this account to distinguish the target, strategy, performed Work, observations, adaptations, and outside results; it is not evidence from an isolated causal experiment.

Treat training followed by supported four-to-six-month workplace projects and expert assistance as a source-described candidate introduction strategy unless independent A.3.1 admission is available. Keep that candidate introduction account, its available description epistemes and separate plans, the SSFD target Method or candidate account, capability evidence, project Systems, performed Work, later reports, named assignment or use relations, target adaptations, strategy adaptations, burdens, and domain results separate.

If an observation exposes a content defect in the candidate introduction account, A.3.2.DE can improve that account without classifying it as a U.MethodDescription. Other description content returns to its own episteme or a local stop; introduction or use alone requires no revision.

Record acceptability or rejection, appropriateness or fit, feasibility, enactment or fidelity, burden or cost, reach, and sustainment only where the source supports each position. The reports do not admit the candidate introduction Method or make every modification a target-Method change. The bounded A.3.1.MI decision can use observations or association without C.28; any claim that SSFD or its introduction strategy caused the reported benefits needs a current C.28 result.

The Digital Vaccine case supplies three sequential action-research cycles in an operating health-services ecosystem. For each cycle, record the Method-related target, the introduction strategy and its status, its separately identified description, and any separate WorkPlan. Then record prioritization, performed introduction or validation Work, observation, target adaptation, strategy adaptation, and revision for the bounded concern. The evaluation remains ex ante and case-specific and establishes neither Method admission, long-term effect, nor transfer to the other elicited domains.

The Halogen and methodology-spread studies add observed adaptation, project demands, practitioner skills, identified organizational conditions where recoverable, drivers, and barriers. For each adaptation record whether it changed the Method-related target, the introduction strategy, its description, a separate WorkPlan, support, or local use, while preserving the recorded kind and status of each. Also record when, planned or reactive status, deciding Agent and authorization basis, affected level, reason, and conditions. Neither source proves a universal sequence or one causal driver of spread.

Implementation-science comparators sharpen this account without supplying its domain ontology. Proctor et al. motivate separate acceptability, appropriateness, feasibility, enactment/fidelity, burden/cost, reach, and sustainment questions. FRAME motivates recording changes to the Method-related target. FRAME-IS supplies the separate question of what changed in the introduction strategy itself. Updated CFIR motivates context and determinant questions; the 2021 MRC framework motivates iterative refinement around key uncertainty and decision usefulness. A.3.1.MI retains the target-versus-strategy distinction while rejecting health-specific entities, a maturity ladder, phase gate, compulsory adoption sequence, and any inference from those taxonomies to FPF Method admission, Work, relation, capability, authority, or culture.

A.3.1.MI:5.1 - APP-ME-01 Early Stop

The EC-417 three-release statement remains a WorkPlan. Do not report introduction, release enactment, later revision, cadence effect, or receiving result until the introduction strategy is identified and actual introduction Work and release Work are admitted with performers, enacted admitted constituent Methods, capability inputs, Systems, named Agent-performed Work occurrences, relation occurrences, assignments, permissions, authority, conditions, target and strategy adaptations, burdens, deviations, and domain results.

The A.15.8.MS support-use task observations may supply identified support baselines and gaps. They do not establish an introduction Method, release Work, AI-provider use, feedback Work, capability, or Method fit. Preserve C-EC-Release-v2 as a target candidate and CUR-EC417-CadenceEffect-1 as unsupported. The application has no supplied A.2.2 capability basis, so a receiving decision that relies on capability returns that missing basis first. If a current adequate basis is supplied and no capability change is needed, retain it without requiring development. Name E.23.CDI or a domain development result and next action only for an actually needed capability change; do not invent capability or prescribe development from the gap alone.

A.3.1.MI:5.2 - Correct outputs with an undelivered learning mechanism

In this constructed example, a team introduces a report-review Method requiring the reviewer to trace each measurement to the equipment identifier and check its unit before recommending release. The proposed introduction strategy combines a lesson with individual rehearsal. Its working explanation is that rehearsal will enable newcomers to recognize identifier and unit mismatches independently. Release still requires a separately qualified reviewer; the introduction attempt has no authority to remove that safeguard.

Records show that the lesson occurred, but individual rehearsal was repeatedly cancelled. Reports released during the attempt have the required corrections. Observation of review meetings shows that experienced colleagues identified the mismatches and newcomers then corrected them. The attendance records and corrected reports therefore concern different contributions: neither establishes independent newcomer capability. The proposed learning mechanism remains unsupported, while the experienced reviewers’ actual corrections are useful observations.

The method engineer connects delivery records, the sequence of detection and correction, current capability evidence and report outcomes. This supports continuing the existing safeguarded review under its established conditions. It also identifies a rival explanation worth considering: supported joint review may supply the immediate checking function while creating a different opportunity for learning. Whether newcomers learn from that participation remains an open question.

Suppose a receiving decision now concerns assigning newcomers independent reviews next month. A feasible comparison uses archived reports with known mismatches, including an unfamiliar unit convention, and records each newcomer’s answer before help, the help actually given and the final correction. The inquiry designer must justify case coverage, comparison, timing, assessment and attainable burden; merely scheduling the exercise is not a result. If the protected inquiry window is unavailable, independent assignment stays unsupported and the existing review can continue.

After such an authorized comparison, suppose the observed records show that newcomers detect familiar identifier mismatches unaided but require expert help for the unfamiliar unit convention. Return that differentiated result to the capability owner and to A.3.1.FT; it supports neither a blanket failure nor unrestricted transfer. C.11.MV includes the expert’s time. A.3.1.MI can develop a proposed introduction variant using joint review and later independent rehearsal. A.3.1.MV determines whether its changed reusable operations constitute a variant; retaining the intended checking and learning functions does not settle that identity question.

The adaptation account records when the joint-review change was chosen and when it actually operated. If rehearsal and coaching change together, the observed benefit belongs to that examined arrangement until a useful comparison separates their contributions. The original lesson remains a delivered event. Its proposed mechanism is reconsidered on the new evidence; the history is not rewritten as if the later strategy had been used from the start.

A.3.1.MI:6 - Bias-Annotation

A.3.1.MI:7 - Conformance Checklist

• Target subjects; either the admitted introduction Method with an A.3.2-classified MethodDescription or the candidate introduction account with its description episteme; a separately governed WorkPlan; performed Work; and named relied-on relations are separated by kind. No pre-admission description is classified as U.MethodDescription.
• Every organizational claim names the organizational System, selected structure, constituent organization, or relation organization actually relied on.
• Every observation position names its maintained result and particular claim or edition, receiving Agent or governing pattern when current, and next action or stop.
• Introduction Work is stated as an authorized attempt intended to establish named conditions; a failed attempt is recordable without contradiction.
• Decision-relevant capability keeps its A.2.2 basis and currentness, or returns the missing basis. Adequate existing capability without a needed change requires no development result. Only a needed capability-change claim consumes a compatible development result or returns its missing/stale basis with a next governing action or stop; irrelevant capability detail is omitted.
• Assignment, permission, authority, access, use, enactment, and other relations name predicates, participants, scope, and obtaining basis.
• Later Work is independently admitted; candidate accounts are not enacted, and only independently admitted Methods may fill an enactment claim.
• Decision-relevant acceptability/rejection, appropriateness/fit, feasibility, enactment/fidelity, burden/cost, reach, sustainment, target-change, and outside-result observations remain separate.
• Every adaptation distinguishes target change from introduction-strategy change and records the affected target, strategy and status, identified description episteme, separate WorkPlan, support or local-use condition; time and planned/reactive status; deciding Agent and authorization; level, reason and conditions; maintained result; and receiving action or stop.
• A relied-on causal or contribution claim uses C.28 and preserves supported and unsupported uses, validity threat and residual uncertainty. An observational result carries only the qualification needed for its receiving use.
• The comparison records the action supported by the available evidence, or the alternatives that remain unresolved and the reason they cannot yet be distinguished. Any further observation or probe has a useful obtainable answer worth its full burden and feasible conditions.
• A.3.1.FT receives a bounded fit or transfer question, C.36.MC a bounded population-level cultural question, and A.3.1.MV/A.15.8.MS/A.15.2 a supported correction, refinement or alternative tied to the particular maintained claim or edition it affects. A.3.2.DE receives a needed correction of MethodDescription or candidate-Method-account content and preserves its status; other content returns to its own episteme or a local stop.
• The result claims no adoption lifecycle, maturity ladder, phase gate, general effectiveness, causal superiority, or authority outside its boundary.

A.3.1.MI:8 - Common Anti-Patterns and How to Avoid Them

A.3.1.MI:9 - Consequences

Method introductions become observable interventions. Teams can learn from use, non-use, adaptation, and outside consequences while keeping the target, introduction strategy and its status, description, any separate WorkPlan, support, capability, authority, identified organizational Systems or selected structures, Work, and domain changes distinct.

The cost is a more explicit baseline and observation design. Some programmes end with bounded association and residual causal uncertainty, and a capability gap can stop introduction even when training was delivered.

A.3.1.MI:10 - Rationale

An intervention can change several subjects, relations, and descriptions at once. Learning requires each claimed change to retain its own subject, governor, baseline, evidence, and receiving use. Otherwise the intervention label becomes a substitute for both Work and explanation.

Separating the Method-related target from the introduction strategy, its status and description, any separate WorkPlan, capability development, and cultural continuation prevents A.3.1.MI from becoming an adoption lifecycle. It remains the practice for introducing one bounded Method-related change, observing later Work and consequences, and using the resulting evidence to correct, refine or develop the particular maintained account or next application.

A.3.1.MI:11 - SoTA-Echoing

Reopen the pattern when practitioners cannot separate target subjects and accounts, introduction strategy and status, description, any separate WorkPlan, performed Work, relation occurrences, observations, and receiving actions; when stronger cross-domain evidence changes the observation or adaptation positions; when repeated introductions reveal an independent organizational-change problem; or when current FPF Method, description, plan, Work, relation, capability, evidence, or causal-use semantics change the action.

A.3.1.MI:12 - Relations

• C.39.MF supplies the Method-of-interest and outside result. A.3.1.MV supplies an admitted variant or status-preserved candidate lineage with applicability and currentness. A candidate account is not enacted; later Work may enact only independently admitted constituent Methods.
• A.3.1.MV governs admitted Method semantics and candidate lineage, provenance, evidence, applicability, currentness, and retirement claims for both target and introduction accounts. A.3.2.DE authors or revises a MethodDescription of an admitted Method, or improves a candidate Method account while retaining its unresolved status. Other description content stays with its own episteme. A.15.2 governs the separate introduction WorkPlan; A.15.8.MS particular support claims; A.3.1.FT bounded fit and transfer questions; and C.36.MC bounded population-level cultural questions. Return a correction, refinement or alternative with the affected maintained claim or edition and the next action.
• E.23.CDI or a domain capability-development pattern governs capability change. A.2.2 governs the relied-on capability result; A.3.1.MI records it as an input, observation, or named gap.
• A.3.1 governs admission of both target and introduction Methods, and A.3.2 governs U.MethodDescription membership. A WorkPlan and performed Work neither admit nor enact a candidate Method. A.13 governs precise Agent claims and A.15.1 every introduction and later Work occurrence. Assignment, permission, authority, access, use, enactment, and other direct relations retain their own named predicates, participants, applicability, and obtaining tests.
• A.3.4 governs a claimed actual bounded change to a continuing subject. Introduction Work, a before/after account, an adaptation record, or a decision label does not by itself identify a U.Transformation.
• A.10 governs evidence use. When the A.3.1.MI decision relies on a causal or contribution claim, C.28 governs the bounded causal-use question, supported and unsupported uses, conditions, validity threats, and reopen trigger. Without that reliance, A.3.1.MI stops at observation or association.
• C.28.CM develops the proposed causal explanation and its rivals. A.3.1.WT can construct the bounded Method trial; a different or more extensive inquiry needs its own qualified design and operational protocol. A.15.9 obtains and qualifies any missing outside-practice result for this use. The selected design and protocol guide the actual trial or inquiry. Its actually obtained observations and their limits then inform the bounded introduction decision; A.3.1.MI:4.5 explains this connection for adaptation. F.0.2.RC is used when a change affects a source-coverage or reconstruction claim.
• Proctor, FRAME, FRAME-IS, updated CFIR, and MRC supply bounded comparator questions only. FRAME and FRAME-IS support the target-versus-introduction-strategy distinction; none creates FPF health ontology, adoption lifecycle, maturity ladder, phase gate, Method admission, Work occurrence, relation occurrence, capability, authority, or culture claim.

A.3.1.MI:End