“A proof of concept or a proof of principle is realization of a certain method or idea(s) to demonstrate its feasibility, or a demonstration in principle, whose purpose is to verify that some concept or theory is probably capable of being useful. A proof-of-concept may or may not be complete….” (from http://en.wikipedia.org/wiki/Proof_of_concept )
“Proof-of-Principle Prototype (Model) (in electronics sometimes built on a breadboard). This type of prototype is used to test some aspect of the intended design without attempting to exactly simulate the visual appearance, choice of materials or intended manufacturing process. Such prototypes can be used to “prove” out a potential design approach such as range of motion, mechanics, sensors, architecture, etc. These types of models are often used to identify which design options will not work, or where further development and testing is necessary.” (from http://en.wikipedia.org/wiki/Prototype )
“Generally speaking, when a new technology is first invented or conceptualized, it is not suitable for immediate application. Instead, new technologies are usually subjected to experimentation, refinement, and increasingly realistic testing. Once the technology is sufficiently proven, it can be incorporated into a system/subsystem.” (from http://en.wikipedia.org/wiki/Technology_readiness_level )
In order to construct a viable proof-of-concept you have to construct a minimal test case, which is small enough to be possible, but large enough to functionally validate the specifications for the idea. The point is that you can scale UP from the minimum, but you cannot scale DOWN. A proof-of-concept an be constructed using physical components or by programming a computer simulation of the proposed system.
A single point of failure (SPOF) is a part of a system that, if it fails, will stop the entire system from working ( http://en.wikipedia.org/wiki/Single_point_of_failure ). The current internet contains many of these single points of failure in its design. In this proposed #NextNet architecture, networks, protocols, and resources, can all be turned on or off to prove that requests receive responses, even with missing connections, and that the network is therefore robust and fails gracefully.
A #NextNet Proof-of-Concept
This is a minimal-requirements use case with three devices to be able to test, model, demonstrate, and explain an architecture for connecting many devices in many ways.