The project organization should work out what information it needs and set up a system to manage documents and records, identify sources of information inside and outside the project, and take both organizations' needs into account. Processes should set controls over how information is prepared, collected, identified, classified, updated, distributed, filed, stored, protected, retrieved, retained and disposed of. Documents and records should show the conditions that applied when they were made, so that whether they hold good for other projects can be checked. Information security should address confidentiality, integrity and availability. Information should be relevant, presented clearly and issued on schedule. Every agreement that affects performance, informal ones included, should be documented formally. Rules for meetings should be set, with agendas sent out beforehand naming who must attend, and minutes recording decisions, unresolved issues and actions with owners and due dates, issued within an agreed period. Data, information and knowledge should be used to set and achieve objectives, the benefit gained from using information should be assessed so that its management improves (clause 8), and the system should be kept as simple as it can be.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.