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

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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.