When linking implementation and migration elements to core and motivation concepts, models must use the permitted relationships: a work package may receive an assignment from an internal active structure, a plateau must be tied to the architecture valid for its time span and may aggregate or compose core concepts, a deliverable or plateau may realize core concepts, a gap must be associated with the concepts that differ between the two plateaus, and composite elements may group work packages or deliverables by aggregation. Plateaus may aggregate or contain goals, outcomes, capabilities and requirements, and deliverables may realize requirements or capabilities; links to motivation elements remain indirect but may be shown explicitly. Weaker association links may be used where a stronger relationship does not apply.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.