EcoHubs

Passed · 2026-06-03

EcoHubs Scope Declaration

Adopts the EcoHubs Scope Declaration — the assets, decision domains, and activities under community governance, and the boundaries explicitly outside it.

Decision type
constitutional
Layers affected
L0
Vote
Supermajority (≥⅔ of votes cast) met
  • Status: Passed
  • Submitted: 2026-05-05
  • Submitted by: Stefan (founding member)
  • Decision type: Constitutional
  • Authorized decision path: Decision Matrix (Layer 2) — “Primary purpose, scope, invariant, or identity constraint changes” → Constitutional; all Full Members; ecohubsOS vote + 30-day ratification; supermajority (≥⅔)

Summary

Adopts the Scope Declaration, naming the seven assets, seven decision domains, and eight activities that fall under EcoHubs governance, plus five areas explicitly placed outside it. Anything not named as in-scope is out of scope by default.

Affected Layers and Artifacts

  • Layer 0 — layers/0-identity/02-scope-declaration.md

Change Type

  • Permanent rule change
  • Time-bounded experiment

Adopted Content

In-Scope Assets

  1. The RCOS specification and all versioned artifacts in this repository
  2. The shared treasury (currently held in the Safe multi-sig wallet)
  3. The ecohubsOS platform (os.ecohubs.community)
  4. The EcoHubs website (ecohubs.community)
  5. The RCOS hosted website (rcos.ecohubs.community)
  6. The EcoHubs brand, domain names, public channels, and social media accounts
  7. Pilot community resources explicitly designated as community-governed

Note on asset 5: at the time of the vote this asset was named blueprint.ecohubs.community. The site has since been renamed to rcos.ecohubs.community. This is a rename of the same governed asset, not a change of scope.

In-Scope Decision Domains

  1. Governance rules and decision processes (Layer 2)
  2. Membership rules, states, and admission (Layer 1)
  3. Treasury and shared resource allocation (Layer 3)
  4. The RCOS specification and its evolution
  5. EcoHubs-owned platforms, websites, and public channels
  6. Support and facilitation offered to existing and emerging communities applying RCOS (meetings, guidance, resources)
  7. Partnerships, external collaborations, and use of the EcoHubs brand

In-Scope Activities and Responsibilities

  1. Maintaining and evolving the RCOS specification
  2. Reviewing and admitting new members
  3. Managing and reporting on the shared treasury
  4. Operating and maintaining community platforms and websites
  5. Facilitating, supporting and documenting pilot communities
  6. Publishing learnings, failures, and adaptations openly
  7. Stewarding the EcoHubs brand, public presence, and social media accounts
  8. Researching and developing new approaches, tools, and methods to make regenerative communities more accessible, resilient, and replicable — including software development and applied experimentation

Explicitly Out of Scope

  1. Underlying server infrastructure, hosting accounts, and third-party service contracts
  2. Personal income, private finances, and private bank accounts of members
  3. Private relationships and personal living arrangements of members (except where safety-critical conditions apply as defined in Layer 4)
  4. Off-network projects and businesses that do not use EcoHubs assets or operate under EcoHubs governance
  5. The internal governance of independent communities that have adopted RCOS — EcoHubs stewards the standard, not the communities using it

Rationale

RCOS-Core §2.2 requires the governed scope to be explicitly declared, and requires that anything not declared in-scope is treated as out of scope. Without this, informal claims of authority accumulate over undeclared assets and decision territory. Naming out-of-scope areas additionally protects members’ private lives and finances, and protects independent communities adopting RCOS from EcoHubs presuming authority over their internal governance.

Risks and Mitigations

  • Risk: An asset or domain is omitted and therefore ungoverned. Mitigation: The default rule (“not declared in-scope means out of scope”) makes omissions visible rather than silent; scope can be extended by a further Constitutional decision.
  • Risk: Out-of-scope item 3 could be used to shield harmful private conduct. Mitigation: The exception for safety-critical conditions under Layer 4 is written into the item itself, and is reinforced by INV-006.

Transition and Migration Plan

No migration required. Status changes from Stub — not yet adopted to Active — adopted 2026-07-03.

Rollback Plan

Rollback requires a further Constitutional decision. Rollback trigger: a ratified finding that the declared scope materially misstates what the community actually governs.

Effective Date

2026-07-03 (end of the 30-day ratification period following the vote close)

Review Date (if experiment or time-bounded)

N/A

Decision Record

  • Vote outcome: Passed
  • Proposal created: 2026-05-05 10:10
  • Vote closed: 2026-06-03 10:10
  • Ratification period: 30 days from vote close, per Decision Matrix (Layer 2)
  • Effective / adopted: 2026-07-03
  • Decision type: Constitutional
  • Mechanism: ecohubsOS vote
  • Decision record: /proposals/passed/2026-05-05_scope-declaration
  • Signatories / vote count: Supermajority (≥⅔ of votes cast) met; per-member tally recorded on the ecohubsOS proposal page

← All passed proposals