A reactive specification formalism for enhancing system development, analysis and adaptivity

During system development, external reviewers, especially ones with expertise in the problem domain or in system and software engineering (SE), often contribute insights that up to that point were not noticed by the engineers and other project stakeholders. These reviewers apparently do so by employing special human competencies that presently are not, or even cannot be, automated. Consider, for example, the competencies that enable the following review comments about a home-assistant robot: (a) during code review: "I see that the robot can defers command execution until it charges its battery for the task; When done charging, does the robot check if the action is still needed?"; (b) following a demo: "Will the robot trip over a thin,transparent phone cord?"; and (c) "Some clear voice commands had to be repeated. Perhaps sometimes the robot isn't listening?".