Reframe governance into sections of bylaws

- Introduce README in bylaws directory
- Clearly include all documents as sections within a whole
- Clarify language around how/where records are kept.

CODE_OF_CONDUCT.md

@@ -3,34 +3,41 @@ status: draft
 ---
 # The Commonhaus Foundation Code of Conduct
 
-The Commonhaus Foundation (CF), and every project within it, needs a clear and enforced Code of Conduct (CoC) to foster a respectful and collaborative environment for all participants.
-
-1. **[Contact Info](#contact-information)**: Defines channels for project issues, foundation-wide concerns, and escalations.
-2. **[Our CoC](#our-code-of-conduct)**: Adopts the Contributor Covenant v2.1 and outlines its scope and enforcement.
-3. **[Member Expectations](#member-expectations)**: Details the behavior expected from members and leaders of the foundation.
-4. **[Reporting](#report-an-issue)**: Describes the process for reporting CoC violations.
-5. **[Responding to Issues](#respond-to-a-coc-issue)**: Provides a guide on handling and documenting CoC reports.
-6. **[Escalation](#escalate-an-issue)**: Offers procedures when regular channels aren't effective or appropriate.
-7. **[CoC Panel](#code-of-conduct-panel)**: Defines the role and composition of the Code of Conduct Panel.
-8. **[Handling Reports](#handling-reports-and-escalations)**: Describes procedures for both regular and escalated CoC reports.
+Welcome to the Code of Conduct (CoC) for the Commonhaus Foundation (CF). This document, forming **Section 8** of the CF [Bylaws][bylaws], reflects our dedication to fostering a respectful, inclusive, and collaborative environment. It sets the standards for behavior expected in our community and provides a framework for addressing and resolving issues in a fair and respectful manner.
+
+- [8.1 Contact information](#81-contact-information)
+- [8.2 Our Code of Conduct](#82-our-code-of-conduct)
+  - [8.2.1 Member Expectations](#821-member-expectations)
+  - [8.2.2 Report an issue](#822-report-an-issue)
+  - [8.2.3 Respond to a CoC issue](#823-respond-to-a-coc-issue)
+  - [8.2.4 Escalate an issue](#824-escalate-an-issue)
+  - [8.2.5 Code of Conduct Panel](#825-code-of-conduct-panel)
+- [8.3 Handling Reports and Escalations](#83-handling-reports-and-escalations)
+  - [8.3.1 Conflict of Interest](#831-conflict-of-interest)
+  - [8.3.2 Reports to `report@mailing-list`](#832-reports-to-reportmailing-list)
+  - [8.3.3 Reports to `coc-escalation@mailing-list`](#833-reports-to-coc-escalationmailing-list)
+- [Contributor Covenant Code of Conduct](#contributor-covenant-code-of-conduct)
+- [Attribution](#attribution)
+
+
+[bylaws]: ./bylaws/README.md
+[cfc]: GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council"
+[cc-dm]: GOVERNANCE.md#decision-making-and-voting
+[coc-reports]: #83-handling-reports-and-escalations
+[cocp]: #825-code-of-conduct-panel "Code of Conduct Panel"
+[membership]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml "Members"
 
-## Contact information
+## 8.1 Contact information
 
-- **Project Issues:** Each CF project will define a `CODE_OF_CONDUCT.md`. For issues related to a project, start there.
-- **Founation Issues:** Issues related to the CF should be sent to `report@mailing-list` for [review](#respond-to-a-coc-issue) by the [Commonhaus Foundation Council][cfc] (CFC).
+- **Project-related Issues:** Each CF project will define a `CODE_OF_CONDUCT.md`. For issues related to a project, start there.
+- **Foundation-wide Issues:** Issues related to the CF should be sent to `report@mailing-list` for [review](#823-respond-to-a-coc-issue) by the [Commonhaus Foundation Council][cfc] (CFC).
   - The CFC will follow [CF CoC procedures][coc-reports] when handling CoC reports.
   - Records will be kept in TODO-private-repository. Access to this repository is restricted to current CFC members.
-- **Escalations:** [Escalations](#escalate-an-issue) should be sent to `coc-escalation@mailing-list` for review by the [Code of Conduct Panel (COCP)][cocp].
+- **Escalations:** [Escalations](#824-escalate-an-issue) should be sent to `coc-escalation@mailing-list` for review by the [Code of Conduct Panel (COCP)][cocp].
   - The [CoCP][cocp] will follow [CF CoC procedures][coc-reports] when handling CoC reports and escalations.
   - Records will be kept in TODO-private-repository. Access to this repository is restricted to CoCP members.
 
-[cfc]: GOVERNANCE.md#commonhaus-foundation-council "Commonhaus Foundation Council"
-[cc-dm]: GOVERNANCE.md#decision-making-and-voting
-[cocp]: #code-of-conduct-panel "Code of Conduct Panel"
-[membership]: https://github.com/commonhaus/foundation-draft/blob/main/MEMBERS.yaml "Members"
-[coc-reports]: #handling-reports-and-escalations
-
-## Our Code of Conduct
+## 8.2 Our Code of Conduct
 
 The CF has adopted the [Contributor Covenant v2.1][v2.1] as its CoC (full text [below](#contributor-covenant-code-of-conduct)).
 
@@ -40,7 +47,7 @@ The CF has adopted the [Contributor Covenant v2.1][v2.1] as its CoC (full text [
 A CoC is meaningful only [when it is effectively enforced](https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415).
 Having a unified CoC allows for consistent enforcement and better support across all CF projects.
 
-### Member Expectations
+### 8.2.1 Member Expectations
 
 All participants in CF projects are bound by the principles outlined in this Code of Conduct.
 
@@ -65,7 +72,7 @@ When decisions are made within the established guidelines and policies of CF pro
 
 This does not mean that decisions are set in stone. CF projects and the CFC are always able to revisit decisions at a later time.
 
-### Report an issue
+### 8.2.2 Report an issue
 
 - Each CF project is free to implement enforcement of the CoC using processes appropriate for the size and scope of the project. CoC enforcement processes and contact methods must be defined in the projects' `CODE_OF_CONDUCT.md`.
 - For CF repositories that do not specify their own `CODE_OF_CONDUCT.md`, send your report to `report@mailing-list`. The CFC will receive these reports.
@@ -74,7 +81,7 @@ Confidentiality is of utmost importance. We also understand that the person repo
 
 - The CF *prohibits retaliation* against individuals who report concerns in good faith.
 
-### Respond to a CoC issue
+### 8.2.3 Respond to a CoC issue
 
 Each complaint will be reviewed and investigated, and will result in a response that is deemed necessary and appropriate to the circumstances.
 
@@ -84,15 +91,15 @@ Access to the private repository should be restricted to individuals charged wit
 
 **Confidentiality:** Given that membership to groups like the CFC or the CoCP have finite terms, members reviewing CoC reports agree to treat all reports as confidential, even after their term is finished.
 
-### Escalate an issue
+### 8.2.4 Escalate an issue
 
 We expect most reports to be handled by the processes put in place by a project or the CFC.
 
 The CF maintains the CoCP to manage escalation when a reporter (a) believes that a report to a member project or the CFC has not been properly handled, or (b) does not feel comfortable reporting an issue through the standard process.
 
 Email `coc-escalation@mailing-list` to escalate an issue to the CoCP. The CoCP will meet to review submitted reports as described in [CF CoC procedures][coc-reports]
 
-### Code of Conduct Panel
+### 8.2.5 Code of Conduct Panel
 
 The CoCP is a foundation-wide team composed of the CFC Chairperson and 4 elected individuals who are not members of the CFC.
 
@@ -101,15 +108,15 @@ CoCP members should consider objectivity and diversity of experience and perspec
 
 Members of the CoCP will be documented in the `cocp-panel` [MEMBERS.yaml][membership] attribute.
 
-## Handling Reports and Escalations
+## 8.3 Handling Reports and Escalations
 
 This section describes the process and roles for handling Code of Conduct (CoC) reports and escalations for both the CFC and the CF Code of Conduct Panel (CoCP).
 
-### Conflict of Interest
+### 8.3.1 Conflict of Interest
 
 Any member of the CFC or CoCP who is involved in the report must recuse themselves from the discussions.
 
-### Reports to `report@mailing-list`
+### 8.3.2 Reports to `report@mailing-list`
 
 All members of the CFC are subscribed to the `report@mailing-list` mailing list.
 
@@ -123,7 +130,7 @@ We understand that the person reporting the issue (**reporter**) may not be the
 6. **Communication of Resolution:** The resolution is shared with the reporter or target. Feedback loops can continue until concerns have been adequately addressed. Absence of feedback within 7 days means resolution acceptance.
 7. **Finalization:** The agreed resolution is implemented.
 
-### Reports to `coc-escalation@mailing-list`
+### 8.3.3 Reports to `coc-escalation@mailing-list`
 
 All members of the CoCP are subscribed to the `coc-escalation@mailing-list` mailing list.