Taking the created concepts as input, the organization should begin validating early, using a first version of the concept; weigh one or more approaches such as studies, pilots, experiments and tests; tackle first whichever uncertainties, hypotheses or assumptions are most critical, in order to learn, gather feedback and build knowledge that lowers uncertainty about how users, customers, partners and others will interact with it, about support and resources, and about its legal, technical, financial, marketing, organizational and time-to-market sides; refine the concept using the lessons, feedback and knowledge gained; judge whether it is feasible and whether the uncertainties still open must be dealt with; and plan more validation where required. Outputs: concepts or proofs of concept validated to the point where the uncertainty left is acceptable for going on to development; relationships built with users, customers, partners and others; and new knowledge.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.