E.20:4.7 - Step 7: Planned baseline & P2W planning-to-work boundary (if planning changes)
If the mechanism introduction changes what one U.WorkPlan pins, the WorkPlan edition is the identifiable planning object. Examples of pins that may change include selected comparator specifications, method descriptions, a time selector and guard pins.
- For a future use of an existing declaration member, introduce or revise
SlotFillingsPlanItemrows as declaration-local ClaimGraph content inside that WorkPlan edition under A.15.3. Use ordinary A.15.2 plan content when only a method or suite choice is being stated. - Give no row an independent kind, record identity, edition, specialization lineage, canonical target, or successor relation. Changing identity-bearing row content changes the WorkPlan’s claim content and is handled as a WorkPlan-edition change under C.2.1 and A.15.2.
- Keep the declaration-local planned-filling content planning-only:
- positive intentions for planned values or designations, using the selected member’s ValueKind, designation rule and semantic cardinality under A.15.3;
- no launch values;
- no
FinalizeLaunchValueswitnesses; - no gate decisions or decision logs; and
- conditions, including time, only when they change applicability or value selection, as specified in A.15.3:4.2; retain material edition pins under A.15.3:4.6 rather than implicit “latest” or “current” resolution.
- Resolve each row through the declaration edition and member selected under A.15.3:4.1–4.4. For an operation argument or expected result, cite the A.6.1 mechanism edition, operation designator and
ArgumentDeclarationorResultDeclaration; no Description wrapper is required. If the member’s meaning or actual-use rule is undefined, returnmissing-governor. - When a receiver needs one row, cite it only through the WorkPlan edition and its stable local-content locator. The locator does not make the row independently resolvable.
The WorkPlan states the planned fillers. Enactment supplies witnesses for the actual runs.