… Use the declaration predicate and ClaimGraph located through A.6.5, A.6.1, or another declared-member source when defining the member; use A.15.2 for ordinary intended work without a planned filling; use A.15.1 for dated work; and use the applicable…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
… remember that Pump_37_Ref is intended for the declaration-local candidate argument. The declaration already states the participant, argument, or result meaning. The WorkPlan states the intention. A.15.3 joins them only as plan content…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
… component, but it gives the PlanItem no separate identity or edition rule. A planned-filling claim says: for this intended future performance and under these conditions, use this value or designation for this declared member. A.15.2 and A.15.3 state that…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
Planning needs a way to preserve intended values without turning every planning field into ontology. Existing RelationSignature SlotSpecs, A.6.1 operation declarations, and other declarations already define reusable member meanings and actual-use predicates.…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
A.15.3:5 - Archetypal Grounding
These constructed cases supply illustrative planning facts; they do not report observed executions…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
Scope. A.15.3 records positive planned designations against existing declared members inside one WorkPlan. When a later question requires comparison, establish actual-use claims under each member's predicate and compare the resulting facts under §4.5.…
In A.15 - System-Role–Method–Work Alignment
A.15:3 - Forces
Force Tension Structure and enactment Stable structural decomposition must remain distinct from system classification, assignment, Method, plan, capability, and dated Work.
Simple and specialized assignments A simple assignment should remain…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
A.15.3:3 - Forces
Force Demand Planning usefulness Preserve the value or designation intended for later work.
Declaration locality Read each member only inside the cited declaration episteme and the pattern that defines it.
Family separation Keep…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
A.15.3:9 - Consequences
Benefit Cost and control Planned choices remain replayable. Each row must point to a declared member and the pattern that defines it.
Declaration families remain coherent. Planners must dispatch relation participants and operation…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
A.15.3:2 - Problem
The following five failures motivate this boundary:
Generic slot creation. Any description field named input, output, role, result, or parameter is treated as a SlotSpec.
Declaration-family collapse. RelationSignature SlotSpecs and…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
A.15.3:11 - SoTA-Echoing
Source contribution Adoption in A.15.3 Rejected shortcut ISO/IEC/IEEE 12207:2017 describes software life-cycle processes, activities and tasks; it is retained as a historical anchor, withdrawn on 29 April 2026 and superseded by…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
A.15.3:12 - Relations
Builds upon: C.2.1 and A.15.2 for WorkPlan identity, present EntityOfConcern, intended-performance designators, and intended-work content; A.6.5 for SlotSpecs inside RelationSignature epistemes; A.6.1 for operation argument and result…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
… effective planned value or later comparison. The declaration pattern defines the member and actual-use rule; A.15.2 and A.15.3 state the intention. If no reusable member is needed, carry ordinary A.15.2 plan content. If typed planned use is needed but the…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
… pattern that defines the plane, calibration or evidence reference, and threshold. Open A.15.3 only when an A.6.1 declaration, a RelationSignature SlotSpec, or another declared member already defines both the position and its actual-use rule. Otherwise return…
In A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member
A.15.3:7 - Conformance Checklist
ID Requirement Practical test CC-A15.3-01 The item is declaration-local WorkPlan content. Its designator resolves inside one cited WorkPlan episteme; no independent PlanItem identity or row authority is claimed.
CC-A15.3-02…