A.15.3:4.2 - State one planned-filling row

A conforming item contains or resolves these values:

SlotFillingsPlanItem:
  planItemDesignator
  workPlanRef
  intendedPerformanceDesignator
  plannedFillingRows:
    - rowDesignator
      targetDeclarationRef
      targetOperationDesignator?
      targetMemberDesignator
      targetMemberFamily:
        RelationSignatureSlotSpec |
        OperationArgumentDeclaration |
        OperationResultDeclaration |
        OtherDeclaredMember
      memberDefinitionPattern
      plannedValueOrDesignation
      planningConditions?
      declarationEditionPin?
      plannedValueEditionPin?
  baselinePolicyRef?
  laterComparisonPolicyRef?

This block represents WorkPlan claim content; it is not an ontic record schema or a second authority for rows. targetMemberFamily is an open local dispatch vocabulary, not a public kind or closed inventory. For an operation argument or result, targetOperationDesignator is required so the member resolves inside the cited mechanism edition; it stays absent for relation SlotSpecs. The memberDefinitionPattern field points to the pattern that defines the member and its actual-use predicate. A.15.3 still states only the plan’s intention.

Read the designation rule from the selected member instead of copying it into the plan. An A.6.5 member uses its refMode; an A.6.1 member uses its bindingDesignationRule. A ByRef value must use the concrete reference kind required there and resolve to the declared ValueKind. A generic Ref, SpecRef, stored token, or merely compatible value does not pass.

Use the selected member’s semantic cardinality. For a single-valued member, conditions and a resolution rule must make at most one planned value effective for one intended use. Alternatives need conditions and a rule that selects among them; row order supplies neither priority nor exclusivity. A multivalued member keeps the declaration’s set, sequence, multiset, repetition, and ordering semantics. If the declaration and cited policy do not decide the needed cardinality, return missing-governor for the member cardinality or selection policy.

Omitting a row leaves that planned filling unstated by this item. It does not say the value or later participant is absent. Prohibition, exclusion, required absence, and closed-world completeness remain separate plan claims with their own applicability and polarity rules.

intendedPerformanceDesignator names the future use being planned; it does not make a future Work occurrence or entity exist. The enclosing WorkPlan keeps its already identified present EntityOfConcern under C.2.1 and A.15.2.

Add time, location, capability, readiness, gate, evidence, source-currentness, bridge, or publication conditions only when changing one would change whether the planned value applies or which value is selected. Cite the separate claims that establish those conditions. planningConditions points to them; it creates none of them and is not a generic condition bundle.

When a baseline or comparison policy selects a planned value or judges a later match, identify its concrete kind, defining pattern, edition, applicability, and reference scheme. A generic PolicyRef or shared label supplies no policy. Pin a declaration or edition-bearing value only when another resolution would change the planned meaning, and make the target reference and pin agree.