A.15.3:4.1 - Use only members that a declaration already defines
Each row points to one member in one declaration edition selected for the intended future use. First choose what is being planned; then open the pattern that defines that member and the rule for its actual use:
| Planned choice | Existing declaration member | What remains defined elsewhere |
|---|---|---|
| participant in a future direct-relation claim | one SlotSpec in one RelationSignature edition | the relation pattern defines participant meaning and the obtaining predicate; A.6.5 defines the local SlotKind, ValueKind, and refMode; A.15.3 records only the planned designation |
| argument in a future operation application | one ArgumentDeclaration in one A.6.1 OperationDeclaration | A.6.1 and the cited mechanism define the argument meaning, ValueKind, designation rule, binding predicate, and cardinality; A.15.3 records only the planned value |
| expected result of a future operation application | one ResultDeclaration in one A.6.1 OperationDeclaration | A.6.1 and the cited mechanism define result meaning and the result-binding predicate; an expected value is not a returned value |
| another declared future use | one declaration member whose own pattern defines both the member meaning and its actual-use predicate | cite that pattern and declaration; if either definition is absent, return missing-governor instead of inventing a target |
A U.MethodDescription is not a target merely because it mentions inputs, effects, parameters, bounds, or acceptance conditions. Nor does a suite description, kit description, table, schema, card, checklist, interface form, or database field expose an A.6.5 SlotSpec unless a cited RelationSignature actually contains that SlotSpec. Operation arguments and results stay in A.6.1 declarations; planning them does not turn them into A.6.5 SlotSpecs.
One item may contain several rows when they serve the same intended performance, baseline policy, and rule for revising the plan. Each row still resolves to its own declared member. Split the item when those three controls differ. The WorkPlan’s present EntityOfConcern remains its C.2.1 identity discriminator; a merely possible future performance does not replace it.