A.1.SCR:0 - Practitioner entry

Use this when. Use this pattern when a decision depends on which exact system acts, is intended to change, carries a capability, persists through a lifecycle, or is being considered or designated as the project system-of-interest—and the proposed subject is still unclear. Ask: Which exact system acts or is intended to change here, and what decision depends on treating it as a system?

First useful move. State the claim, the proposed actor or change bearer, and what you will decide differently if it is or is not a system. If the phrase already names Work, a Method, capability, transformation, episteme, structure, or a direct relation and your decision does not depend on systemhood, name that object and leave through its subject pattern. Apply the complete A.1 criterion only in the system-dependent branch.

First-minute recognized case. A maintenance decision asks whether Pump-37 or the larger pumping assembly must be isolated before repair. The exact pump has identified constituents, obtaining part relations and assembly, a reidentification rule across seal replacement, a composition-grounded pumping characteristic, and governed boundary/interface facts. Its organization can causally participate in pumping and maintenance Work while preserving identity. The first result is: Pump-37 is the recognized U.System whose boundary controls this isolation decision.

Subject-pattern and proposed-system readings. “We develop the surgeon’s mastery” ordinarily concerns the person and their actual ability, training Work or evaluation. Use A.2.2 for the ability under stated conditions; an account of it has that independently identified person as its subject. Training can change the ability while the report stays unchanged; editing the report alone changes no ability. Select the assertion episteme as subject only when the question concerns that assertion. If the source instead proposes the physically or operationally realized whole SutureControl-M17, identify that exact U.Entity and evaluate it—not a substituted surgeon or capability—under the already admitted U.System kind. Choose the reading on which the current decision depends.

Near-identical non-system case. PumpKit-37 contains parts of the same types and carries the same product label, but its constituents are not assembled by the required part relations, it has no composition-grounded pumping characteristic, and it cannot participate in the plant installation while preserving pump identity. The first result is: the kit is not the pump system; the current subjects are the material collection and its description.

Honest unknown case. WorkshopController-9 is an exact boxed device, but the team cannot recover its internal assembly, reidentification rule, or operating boundary. The evaluation is unknown and names those missing inputs; the decision that assumes an acting controller remains blocked. The entity itself satisfies or fails the criterion independently of current knowledge.

What this buys. A real actor, change bearer, lifecycle subject, capability holder, or project system-of-interest decision gets a tested identity and boundary. A direct Work, Method, capability, structure, episteme, or relation question leaves immediately without an unnecessary A.1 evaluation. Continue through A.1.STM only if the practitioner still cannot connect this recognition result to the project’s outside use; recognition alone does not open the long map.

Not this pattern when. If the subject and its admitted kind are already clear, use the subject pattern of the claim. If service or access wording hides a promise, participant, bearer, permission, Work occurrence, status, evidence, or direct relation, begin with A.6.P §4.11a. Enter A.1.SCR from that route only when the repaired claim itself depends on whether the exact entity recovered by A.6.P—an exact bearer or access-providing arrangement—is a system. If only a name for an already recoverable object is unclear, use F.18.