A change proposal may come from the organization itself, from a customer, or from an external provider. Each change proposal should be identified, and kept as documented information, before it goes to the dispositioning authority; a proposal usually gives the configuration items and information affected, with their titles and present revision status, a description of the change, any further items or information it may affect, who proposed it and when, why it is needed, and its category. Its processing status, the decisions taken and its disposition should be kept too, usually on a standard form carrying a unique number so it can be traced.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.