Implementation and migration models must use work packages for one-off behavioral units with defined start and end dates that realize goals or deliverables, deliverables for precisely defined results, implementation events for instantaneous state changes, plateaus for stable architecture states over a limited period, and gaps for the difference between two plateaus. Implementation events may carry a time attribute and should preferably be named as completed actions. Work packages may be divided into sub-projects or tasks and may represent projects, programs or portfolios.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.