docs(policy)_: Replaced section on enforcement with consensus

'4. Enforceability and Respect for Policies' with 'Upholding Policies Through Consensus'

_docs/policies/README.md

@@ -4,11 +4,51 @@
 the creation, amendment, and enforcement of all actions within the
 `status-go` repository. These policies reflect our core values of
 inclusivity, transparency, and consensus-driven decision-making while
-defining enforceable rules that guide status-go contributions. Policies
+defining enforceable rules that guide `status-go` contributions. Policies
 are not merely guidelines but are to be respected and adhered to, ensuring
 alignment across contributors.
 
-## 1. Inclusivity
+## Upholding Policies Through Consensus
+
+### Collective Agreement
+
+The enforceability of policies stems not from the authority of any
+single individual or group but from the collective agreement and shared
+commitment of all `status-go` contributors. Policies are not imposed
+unilaterally but are the result of transparent discussions and explicit
+recorded approval from key stakeholders. This includes team leads,
+members of the @status-im/status-go-guild GitHub team, and other
+relevant contributors.
+
+### Shared Responsibility
+
+Respecting and adhering to policies is a shared responsibility
+that reflects the values and goals of `status-go` contributors. Approved
+policies are not merely recommendations but agreed-upon standards,
+created through mutual understanding and collaboration, that guide
+how we work together and contribute to the project.
+
+### Mutual Enforcement through Alignment
+
+The power of enforcement does not rest with any one authority; it
+arises from the collective commitment of all contributors to uphold
+policies that have been collaboratively crafted and agreed upon. This
+ensures that policies are respected not out of obligation but because
+they represent the shared vision and trust of the contributors.
+
+### Fostering Alignment
+
+Policies are designed to ensure consistency, fairness, and alignment
+across the teams, creating a framework that supports effective
+collaboration and decision-making. By honouring the principles of
+inclusivity and consensus, we strengthen trust and accountability
+within all contributors.
+
+By grounding our policies in transparency, mutual respect, and collective
+ownership, the `status-go` project ensures they are both enforceable and
+reflective of the shared goals of all contributors.
+
+## Inclusivity
 
 Every `status-go` contributor must have an equal opportunity to
 participate in the creation and review of policies. Contributions
@@ -22,7 +62,7 @@ opinions and suggestions.
 language, and the decision-making process should be easy to understand
 for everyone involved.
 
-## 2. Transparency
+## Transparency
 
 All discussions, decisions, and processes related to policy creation
 must be fully transparent. This includes:
@@ -34,7 +74,7 @@ anyone can review the rationale behind a decision.
 rationale, must be clearly communicated to the contributors through
 appropriate channels.
 
-## 3. Consensus
+## Consensus
 
 Policies must be created and modified through a consensus-based approach,
 ensuring that contributors agree on how to move forward. The following
@@ -48,19 +88,3 @@ made to find a compromise that balances the needs of all stakeholders.
 meaning that while not everyone may agree 100%, all should feel their
 voices were heard and respected, and the final decision reflects
 contributors’ general will.
-
-## 4. Enforceability and Respect for Policies
-
-- **Key stakeholder approval**: The guild does not have unilateral
-enforcement power. Instead, policies require explicit recorded
-approval from all key stakeholders before becoming enforceable. This
-includes team leads, members of the @status-im/status-go-guild
-GitHub team, and other relevant parties.
-- **Respect and adherence**: Policies are not optional guidelines.
-Once approved, they are enforceable rules that all contributors to
-the status-go project are expected to respect. This ensures consistency,
-fairness, and alignment with all contributors' shared goals.
-
-By adhering to these foundational principles, status-go policies
-create a framework that balances inclusivity, transparency, and
-consensus with the need for enforceable and respected policies.

_docs/policies/submitting-policy.md

@@ -39,6 +39,7 @@ proposal PR.
   - MUST receive a minimum of six approvals from CCs.
 
 # Policy Overrides
+
 On rare occasions, circumstances may necessitate that an established
 policy is circumvented when merging a feature PR. This is considered
 an **override** and MUST follow the process outlined below to ensure