diff --git a/cic-charter.md b/cic-charter.md
index e421d9b..e750e80 100644
--- a/cic-charter.md
+++ b/cic-charter.md
@@ -20,16 +20,28 @@ The CIC Commons presents a collection of tools to create community inclusion cur
 - Ensure that any software services are not monopolized and that communities are empowered to run their own services
 
 ## Community Statement
-The CIC Commons is an open group that identifies key roles that make up the community: software engineers, practitioners, field & support engineers, designers and artists, system administrators, web designers, writers, speakers, translators, volunteers and more.
-Grassroots Economics Foundation specifically identifies both employees and community volunteers
+The CIC Commons is an open group that identifies key roles that make up the community: software engineers, practitioners, community groups, field & support engineers, designers and artists, system administrators, web designers, writers, speakers, translators, volunteers and more.Organizations such as [Grassroots Economics Foundation](http://grassecon.org) identify employees and community bounty programs to support the CIC Commons based on avalible funding from grants. Community members are extreemly important to the CIC commons as they are the commons - your imput and support is needed to make these tools useful.
+
+### Elinor Östrom’s Commons Governance Rules. 
+ 1. Who is part of the CIC Commons and who is not? What are the rules for joining? (Define clear group boundaries.)
+	1. Anyone that wants to contribute to CIC Software, learnings, best practics, research implementation is welcome 
+ 1. Are the rules governing the CIC Commons and usage appropriate? (Match rules governing groups and the use of community resources to local needs and conditions.)
+    1. Currently only a few lead architects approve pull requests and merges. They have been assigned by Grassroots Economics Foundation so far but are in the process of self defining and establishing rules for self-governance.
+ 1. Who can participate in modifying those rules? (Ensure that those affected by the rules can participate in modifying the rules.)
+    1. To be developed. Anyone can discuss the rules for modifying the software or fork the code base. 
+ 1. How are CIC Commons rules legitimate outside the community or group creating them? (Make sure the rule-making rights of the community members are respected by outside authorities.)
+    1. CIC Implementers like Grassroots Economics Foundation are supported to ensure security and as much legal compliance as is possible.
+ 1. How are CIC Commons member behaviours and rule compliance monitored? (Develop a system, carried out by the community to monitor member’s behaviour such as trade balance.)
+    1. Software modififications are required to have oversight and pass test coverage.
+ 1. How are disputes resolved in the community? (Provide accessible low-cost means for dispute resolution.)
+    1. To be developed
+ 1. What kind of governance layers are there for maintaining the CIC Commons? (Build responsibility for governing the common resource in nested tiers from the base level to the entire ecosystem.)
+    1. To be developed
+
 
 ###Notes:
 Expand on how a community around the product increases the value of the overall work. Why does having other people support the development matter to the CIC Engine? How does collaboration and teamwork make an impact to the CIC Engine? You have defined the people in your community, now help me understand how those people fit into the bigger picture.
 
-(write about software stack as a commons for chain interaction)
-(make clear that frontends are out of scope for this spec)
-(make clear that further extensions - like custodial webapp client, telegram bot client etc - is out of scope of document)
-
 ## CIC Summary
 CIC is a custodial wallet and blockchain bidirectional interface engine for community inclusion currencies
 
@@ -41,6 +53,7 @@ CIC is a custodial wallet and blockchain bidirectional interface engine for comm
 - Includes a broad collection CLI tools for most common chain and engine operations
 - Empowers implementers to choose their level of abstraction
 - Supports both local, containerized and decentralized environments
+- Support last mile front-end apis and integrations
 
 ## System parts