A.6.1:4.7 - Keep mechanism, application, method, work, and description questions separate
One project concern can need several linked values. Recover each by its working question:
| Working question | Governing object and pattern |
|---|---|
| What reusable operation declaration is current? | U.Mechanism under A.6.1. |
| What particular operation application and actual argument or result values are current? | The exact declaration-local application and operation-application binding occurrences under A.6.1. |
| What semantic way of doing is selected? | U.Method under A.3.1. |
| What episteme describes that method? | U.MethodDescription under A.3.2. |
| What work is intended? | U.WorkPlan under A.15.2. |
| What dated work occurred? | One Work occurrence admitted under U.Work by A.15.1. |
| What entity realizes the mechanism? | The entity’s direct kind plus the mechanism-realization relation in A.6.1. |
| What supports a claim about admission, application, result, or realization? | Domain-local evaluation, measurement, evidence, assurance, and currentness relations under their direct patterns. |
| How is the mechanism represented or published? | A.6.3, A.6.3.RT, and E.24.PUB. |
A MethodDescription may cite a mechanism declaration. A Method selection requires an independently established selector result. When an actual A.6.1 application supplies that result, it must apply a declared selector operation whose obtaining result or SelectionSlot binding identifies the exact selected Method. A direct constraint relation may separately constrain the Method. An operation declaration may type a U.Method as an argument or result only when that is the operation’s declared meaning; an actual application may bind the Method under that declared argument or result meaning. Planned assignment, actual enactsMethod, and a dated Work occurrence require their own governing predicates. One Work occurrence admitted under U.Work may enact the Method; the claim about that occurrence may cite the independently identified application and bindings under A.15.1. For that Work claim, recover each required actual performer and the temporal extent, enactment, and locally declared Work-to-System containment basis under A.13/A.15.1 as in §4.5; precise assignment-bound attribution remains conditional there. Add resource-use, affected-referent, continuity, and neighboring result or effect claims only when the account asserts them, each under its own governing predicate.