A.1.1:0 - Practitioner entry

Working reader and current decision. This pattern is for a domain architect, systems engineer, or service owner deciding whether several facts about one model must be treated together for the next engineering move. The reader starts from that decision—change scope, release scope, ownership boundary, integration boundary, or whether two uses belong together—not from a team name, repository, diagram, or the word context.

Governed object in plain language. A.1.1 governs the selected organization of where one exact model applies, how it is actually used in assigned Work, and whether concrete expressions still agree with it. The Tech name is BoundedModelUseStructure; the familiar Plain retrieval name is bounded context. It is a U.Structure, not a container for systems, teams, Work, documents, or publications.

First useful move — take the smallest branch.

Name one exact model edition and one exact place or thing about which it is used.
Ask what the present decision needs. If applicability alone answers it, recover ModelApplicabilityRelation and stop. If actual use is current, recover the exact actual performer through A.13 and let A.15.1 independently admit the performed Work; because ModelUseRelation expressly represents assignment-bound use, then establish F.6 through the same obtaining A.13 assignment and recover ModelUseRelation, then stop. If maintained expression content is current, recover the fixed model content, fixed expression content, declared coherence predicate, and comparison scheme, then decide ModelExpressionCoherenceRelation and stop.
Recover the remaining direct relations only when their joint organization changes the decision. Select BoundedModelUseStructure only then.
Keep every boundary crossing separate. A proposed source, target, direction, required fit, permitted loss, and claim scope is useful planning content, but it is not an occurrence and cannot identify either endpoint structure.

First-minute success case. A press-control team must decide whether a controller-code change may be handled as a local code edit or must enter the independently governed release review together with model applicability and operating use.

PressControlModel-5 is the exact claim-bearing model edition, Press-3 is the use locus, and the model applies within SafetyControlClaimScope; this is one ModelApplicabilityRelation occurrence.
A.13 first recovers Operator-12 : U.System as the exact actual performer through obtaining OperatorAssignment-8, and A.15.1 independently admits PressOperationWork-91 : U.Work. Because this actual-use claim expressly represents assignment-bound use, exact F.6 performedUnderAssignment(PressOperationWork-91, OperatorAssignment-8) then obtains. The already recovered performer actually uses PressControlModel-5 during that Work concerning Press-3; this is one ModelUseRelation occurrence.
ControllerImplementsControlModelPredicate checks the fixed contents of PressControlModel-5 and PressControllerCode-17 under PlantControlReferenceScheme. It returns true, so one ModelExpressionCoherenceRelation occurrence obtains. The predicate is the test value, not the occurrence or an evaluation procedure.
Because independently governed PlantReleaseRule-3 needs model applicability, operating use, and fixed-content coherence together when each is material, select their organization and present those three facts jointly to the release review. This selection supplies the review’s subject matter; PlantReleaseRule-3 supplies the review obligation; release authority, if needed, is established separately.

Named selection-use frame	Exact question	Admissible action	Stop or return condition
`PressControlReleaseFrame`	Must this change be considered as code alone, or together with current applicability, operating use, and fixed-content coherence?	Give the three exact occurrences and applied constraints as the joint subject matter of the independently governed release review.	Return to the three direct relations if `PlantReleaseRule-3` is absent or does not require their joint review.

This row names the selection-use frame reconstructed in the full assurance replay in section 5.1; the first-minute action does not require unpacking its A.22 identity proof. If the decision asked only whether the model applies to Press-3, stop after step 1. If PlantReleaseRule-3 were absent or did not require the three facts together, stop at the direct relations. No crossing is asserted.

Three quick recognition situations.

Situation	First direct result	When the structure becomes current
Industrial control	Applicability, assigned-Work use, or fixed-content coherence for one control model and machine.	Their exact three-relation organization, exact applied constraint claims, and a filled selection-use frame change an engineering decision.
Clinical and billing terminology	Separate F.6 attributions, A.1.1 use occurrences, and A.2.6 scopes for diagnosis and billing Work.	Each positive structure has its own complete three-relation organization, applied constraints, and selection-use frame; a shared model does not merge them.
Published classification model	Actual assigned-Work use of one published model concerning an organization.	Applicability, use, coherence, constraints, and one classification-use frame jointly change the classification decision; publication alone is insufficient.

Short glosses. A model episteme is one exact claim-bearing model edition. A model-use holon is one already admitted system or other concrete whole about which the model applies or is used; it is not a context container. Work (U.Work) is one exact dated doing, not its method, plan, or result. A claim scope (U.ClaimScope) is the set-valued boundary of context slices for one claim. A relation occurrence is a world-side relation actually obtaining under its predicate. A reference scheme is the interpretation basis for claim content. A structure here is a selected organization of already governed constituents, obtaining relations, applied constraints, and one exact selection-use frame; it is not another whole.

Adoption test. After applying A.1.1, name the exact organization that changes the present decision and the condition for stopping or returning to its direct relations. If either is missing, stop at the direct relation or the pattern that defines or tests it. Use F.19:4’s plausible-reader test for any optional explanatory guard.

Names for retrieval. The Plain label is bounded context and the Tech label is BoundedModelUseStructure. Use F.18 for designation settlement and lineage, and F.17 for the public terminology row and its refresh evidence; A.1.1 keeps only the names needed to apply this pattern. Authors MUST NOT publish U.BoundedContext as a U-kind.