First draft

README.md

@@ -1,2 +1,12 @@
 # patio-circles
 Documentation of Patio's Sociocratic Circles
+
+Patio uses a loose and informal version of [Sociocracy](https://en.wikipedia.org/wiki/Sociocracy)
+
+The "root" decision-making body is called the [Member Circle](member_circle.md) and consists of all the members of Patio: [list members here]
+
+The Member Circle created a child [Coordination Circle](coordination_circle.md) to handle the coordination of meetings and projects.
+
+The Member Circle created a child [Community Landing Page Circle](community_landing_page_circle.md) to handle the development of a landing page for Patio.
+
+The Community Landing Page Circle created 3 child circles to take on the work of creating the site: a [Design Circle](design_circle.md), a [Content Circle](content_circle.md), and a [Technical Circle](technical_circle.md)

aim.md

@@ -0,0 +1,7 @@
+# AIM
+
+A Circle's AIM is its reason for being. The AIM is the direction the circle should go.
+
+It is the job of the [COORDINATOR](coordinator.md) to help support the circle in keeping pointed toward the circle's AIM.
+
+It is the job of the [FACILITATOR](facilitator.md) to help support the circle's meetings pointed toward the circle's AIM.

community_landing_page_circle.md

@@ -0,0 +1,23 @@
+# Community Landing Page Circle
+
+The Community Landing Page Circle was created by the [Member Circle](member_circle.md) in order to oversee the creation of a landing page for Patio.
+
+The Community Landing Page Circle's [AIM](aim.md) is:
+
+> Create a landing page for Patio
+
+The Community Landing Page Circle's [DOMAIN](domain.md) is:
+
+> Any decisions regarding the implementation of the landing page
+
+The Community Landing Page Circle's [TERM](term.md) is: ???
+
+The Community Landing Page Circle's [COORDINATOR](coordinator.md) is: ???
+
+The Community Landing Page Circle's [FACILITATOR](facilitator.md) is: ???
+
+The Community Landing Page Circle's [SCRIBE](scribe.md) is: ???
+
+## Child Circles
+
+The Community Landing Page Circle created 3 child circles to take on the work of creating the site: a [Design Circle](design_circle.md), a [Content Circle](content_circle.md), and a [Technical Circle](technical_circle.md)

content_circle.md

@@ -0,0 +1,21 @@
+# Content Circle
+
+The Content Circle was created by the [Community Landing Page Circle](community_landing_page_circle.md) to handle the site content.
+
+The Content Circle's [AIM](aim.md) is:
+
+> Provide content for the landing page
+
+The Content Circle's [DOMAIN](domain.md) is:
+
+> All matters related to the content of the landing page
+
+The Content Circle's [TERM](term.md) is: ???
+
+The Content Circle's Members are: `Naska Nico Gille Jorge Marko Keegan Livia`
+
+The Content Circle's [COORDINATOR](coordinator.md) is: ???
+
+The Content Circle's [FACILITATOR](facilitator.md) is: ???
+
+The Content Circle's [SCRIBE](scribe.md) is: ???

coordination_circle.md

@@ -0,0 +1,18 @@
+# Coordination Circle
+
+The Coordination Circle was created to coordinate meetings and projects for Patio.
+
+The Coordination Circle's [AIM](aim.md):
+
+> The aim of this coordination group is to collect and merge the big picture, get together, identify where the community would like to go and help it fulfill its needs.
+> Spanish: El propósito de este grupo de coordinación es recopilar y sintetizar el panorama general de la comunidad, reunirla, identificar hacia a dónde quiere ir y ayudar a satisfacer sus necesidades.
+
+The Coordination Circle's [TERM](term.md): `3 months starting in August 13th 2021` NOTE: overdue!
+
+The Coordination Circle's Members: `David, Yasu, Marti, Naska, Nico - Aaron?, Ujjwal?`
+
+The Member Circle's [COORDINATOR](coordinator.md) is: Nico with Yasu as backup
+
+The Member Circle's [FACILITATOR](facilitator.md) is: David with Naska as backup
+
+The Member Circle's [SCRIBE](scribe.md) is: Martu with Naska as backup

coordinator.md

@@ -0,0 +1,7 @@
+# COORDINATOR
+
+The job of the COORDINATOR of a circle is to support and make sure the Circle is still headed towards its [AIM](aim.md).
+
+Importantly, the COORDINATOR does NOT make decisions for the Circle. The Members of a Circle must all consent to a decision.
+
+The COORDINATOR simply supports and keeps the Circle on track.

design_circle.md

@@ -0,0 +1,21 @@
+# Design Circle
+
+The Design Circle was created by the [Community Landing Page Circle](community_landing_page_circle.md) to handle the site design.
+
+The Design Circle's [AIM](aim.md) is:
+
+> Provide a beautiful design for the landing page
+
+The Design Circle's [DOMAIN](domain.md) is:
+
+> All matters related to the look and feel and design of the landing page
+
+The Design Circle's [TERM](term.md) is: ???
+
+The Design Circle's Members are: `Meric Tomás David Natalia Manuel`
+
+The Design Circle's [COORDINATOR](coordinator.md) is: ???
+
+The Design Circle's [FACILITATOR](facilitator.md) is: ???
+
+The Design Circle's [SCRIBE](scribe.md) is: ???

domain.md

@@ -0,0 +1,7 @@
+# Domain
+
+A Circle's DOMAIN is its domain of authority. When a Child Circle is created, the members of the Parent Circle must consent to what authority they are delegating to the Child Circle. Anything that isn't delegated to a Child Circle is the responsibility of the Parent Circle.
+
+It is important that if there are multiple Child Circles, that their DOMAINs have clear boundaries, otherwise the responsibilities may overlap.
+
+Also, it is important that if the parent circle does not want to get involved in too many decisions, that the DOMAINs of the child circles sufficiently cover what the Parent Circle wants to delegate.

facilitator.md

@@ -0,0 +1,7 @@
+# FACILITATOR
+
+The job of the FACILITATOR is to ensure that a Circle's meetings are pointed in the direction of the Circle's AIM.
+
+The FACILITATOR should ensure that all members of a Circle have their voices heard.
+
+The FACILITATOR should keep the meetings efficiently and on-time, making sure the space is safe and respectful for everyone.

member_circle.md

@@ -0,0 +1,21 @@
+# Member Circle
+
+The Member Circle is the main decision-making body of Patio.
+
+Members of Patio are:
+
+`Fran from Matelab. Leo from Codesoft. Jorge from Tierra Común. David from Colab. Ujjwal from Igalia. Yasu from TNG. Nico from Fiqus. Meriç from Albatros Turkey.`
+
+The Member Circle's [AIM](aim.md) is:
+
+> "Be closer to each other. People get to know each other. Not only work but also create great things together. Evolve the collaboration. Create an environment of easy collaboration. Create a confederation (federation of federations). Help create federations of coops in each country to strengthen the coop movement in each territory, so we can become a network of networks. Strong human connection to achieve confidence to share project opportunities, knowledge, experience. Translate ideas into actions, accomplish things together"
+
+The Member Circle's [DOMAIN](domain.md) is everything that isn't delegated to its child circles: [Coordination Circle](coordination_circle.md) or [Community Landing Page Circle](community_landing_page_circle.md)
+
+The Member Circle's [TERM](term.md) is: Indefinite
+
+The Member Circle's [COORDINATOR](coordinator.md) is: ???
+
+The Member Circle's [FACILITATOR](facilitator.md) is: ???
+
+The Member Circle's [SCRIBE](scribe.md) is: ???

scribe.md

@@ -0,0 +1,7 @@
+# SCRIBE
+
+The job of the Circle's SCRIBE is to record relevant information that is important to the Circle.
+
+For instance, the SCRIBE may take notes during a meeting, or record decisions that have been consented to by the Circle.
+
+This could include the creation of Child Circles, keeping track of TERMS for Circles or Proposals, etc.

technical_circle.md

@@ -0,0 +1,21 @@
+# Technical Circle
+
+The Technical Circle was created by the [Community Landing Page Circle](community_landing_page_circle.md) to handle the site's technical implementation.
+
+The Technical Circle's [AIM](aim.md) is:
+
+> Provide the technical implementation for the landing page
+
+The Technical Circle's [DOMAIN](domain.md) is:
+
+> All matters related to the technical implementation of the landing page
+
+The Technical Circle's [TERM](term.md) is: ???
+
+The Technical Circle's Members are: `Yasu Chris Ben Livia`
+
+The Technical Circle's [COORDINATOR](coordinator.md) is: ???
+
+The Technical Circle's [FACILITATOR](facilitator.md) is: ???
+
+The Technical Circle's [SCRIBE](scribe.md) is: ???

term.md

@@ -0,0 +1,9 @@
+# TERM
+
+A TERM is simply a period of time that a Proposal or Circle has before it is reviewed for effectiveness.
+
+All decisions should have a TERM associated with them. This makes it much easier for Members of a Circle to consent to passing the proposal.
+
+Circles themselves should also have TERMS. After a TERM is completed, the Parent Circle should be given an opportunity to review the Child Circle and determine if it is still useful in fulfilling its AIM.
+
+At the end of a TERM, the Members of a Circle (for Proposals) or the Parent Circle (for Child Circles) can of course consent to keeping the Proposal or Child Circle in place if it is fulfilling the AIM intended.