Agilently ConsciousSoftware design methodology, Agile used to construct systems in philosophy.A software development model called Waterfall was initially dominating the approaches used while the big software projects were undertaken. Within a few years became evident that the Waterfall model (finish all designs before you start coding) challenges the human imagination and memory to the point of becoming a burden rather than help. The Agile Methodology came within a wide spectrum of methodologies proposed as a replacement for Waterfall. Most of these proposed methodologies were similar in that that they require a gradual and cyclical conversion of concepts to final though extensible, computer-executable pieces of software.The author draws a parallel between Waterfall Methodology in software and a traditional way the philosophical systems were built: a single, intellectual hero was spending a lifetime construction one system. The author proposes and invites everyone who would like to participate to form one, or given that differences are likely to emerge, several Agile teams focused on erecting new philosophical systems. The below essay is just a starting point, a seed for one team. As it is with Agile software construction the order of operations, methods, ways of achieving the sub-goals, and definitions of sub-goals are the main subject of constant negotiation between team members. The final goal of the project is defined as a system that proves that the fabric of the society is so tightly woven and consists of symbiotically dependent nodes to the point that we can consider it a single organism. From there very prescriptive recommendations can be formed on how to maximize the collective wellbeing and happiness of individuals. Rules: 1.This system is expected to target political and social phenomena.2.As the concerned phenomena constitute usually conflicts the system must dignify BOTH sides in the conflict and present them with arguments that were not pondered by them before and that are conciliatory.3.The team member (developer, to save on words) can remain anonymous or publicly sign his chapters, or paragraphs. Once a part of the text is signed it becomes exclusive; that is only the author can modify it.4.Maximum 4 pages per two weeks are allowed.5.The scrum master (the editor) might reject contribution without naming a reason.Advice:1.Read what others wrote to avoid duplications at the minimum and place your contribution in the most relevant place at the best.2.Present arguments, avoid dramatizationMotivation: For millennia, humanity forms states. The neighboring states engage in wars roughly every 20, 30 years. While the leadership offers, every time, some practical explanation majority of the time the war can be traced back to the change of ruling person or a team. For millennia we, humans know about the problem and we tried to find a solution. Ancient Egypt, its contemporaries, and way into the seventeenth century the world favored "eternal" dynasties as a solution. Now the opposite, a frequently changed, electable administrators are seen as the best way to avoid a monumental struggle for power. Yet, the wars did not end. What else do we need to learn about our species to avoid this self-mutilation?Invitation: Have a read, extend, or challenge anything you find in the text. Go on your own with a separate publication if inspired to do so after reading or join the team. Plagiarism is not allowed. You need to indicate the source if you decide to quote verbatim or in principle.References: https: //www.agilealliance.org/agile-essentials/agilealliance.orgThe contact email is on the last page of the kindle book.