**RCOS — Regenerative Community Operating System**

# Scope Declaration

- **Generated:** 2026-04-29
- **Source (latest version):** [https://blueprint.ecohubs.community/articles/rcos-templates/layer-0/scope-declaration](https://blueprint.ecohubs.community/articles/rcos-templates/layer-0/scope-declaration)
- **All RCOS templates:** [https://blueprint.ecohubs.community/articles/rcos-templates](https://blueprint.ecohubs.community/articles/rcos-templates)

---
- **Layer:** 0 — Identity & Scope
- **Status:** Template — adapt for your community
- **RCOS reference:** [§2.2](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration), [§2.5](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#25-artifacts)

---

## In-Scope Assets

*RCOS clauses: [2.2.1](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration), [2.2.2](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration), [2.2.4](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration)*

<details data-kind="rationale">
<summary>Why enumerate every governed asset?</summary>

If the community has not explicitly named an asset as in-scope, it isn't — full stop. Listing assets by name closes the gap where informal claims of authority grow over undeclared resources, and gives members a concrete checklist to verify what the community actually controls.

</details>

<details data-kind="instructions">
<summary>How to fill this in</summary>

List every asset the community collectively governs: shared funds, treasuries, land, real estate, software, websites, social accounts, brand, intellectual property, physical infrastructure, etc. Be specific — name accounts, wallets, domains.

</details>

1. _<Asset 1, e.g. the shared treasury held in a specific multi-sig wallet.>_
2. _<Asset 2, e.g. the community website and its domain.>_
3. _<Asset 3, e.g. shared physical infrastructure or land.>_
4. _<Asset 4.>_

## In-Scope Decision Domains

*RCOS clauses: [2.2.1](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration), [2.2.2](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration)*

<details data-kind="rationale">
<summary>Why name decision domains, not just assets?</summary>

Scope isn't only about stuff — it's about which kinds of questions the community gets to answer collectively. Naming decision domains makes it unambiguous where collective authority applies and where an individual or external party still decides, preventing quiet capture of decision territory.

</details>

<details data-kind="instructions">
<summary>How to fill this in</summary>

List the categories of decisions the community has authority over. These map to later layers (governance, membership, treasury, etc.) — name them at a level that makes it clear what kinds of questions the community decides together.

</details>

1. _<Decision domain 1, e.g. governance rules and decision processes (Layer 2).>_
2. _<Decision domain 2, e.g. membership rules and admission (Layer 1).>_
3. _<Decision domain 3, e.g. treasury and shared resource allocation (Layer 3).>_
4. _<Decision domain 4.>_

## In-Scope Activities and Responsibilities

*RCOS clauses: [2.2.1](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration), [2.2.2](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration)*

<details data-kind="rationale">
<summary>Why declare the work the community owns?</summary>

Authority without owned responsibility produces paralysis; responsibility without declared authority produces burnout and blame. Listing the activities the community collectively governs makes the work visible, assignable, and accountable — and makes it obvious when something important has no owner.

</details>

<details data-kind="instructions">
<summary>How to fill this in</summary>

List the ongoing activities the community is responsible for: maintaining shared infrastructure, admitting members, reporting on resources, stewarding the brand, etc. These are the things that need an owner via Layer 5.

</details>

1. _<Activity 1.>_
2. _<Activity 2.>_
3. _<Activity 3.>_
4. _<Activity 4.>_

## Explicitly Out of Scope

*RCOS clauses: [2.2.3](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration), [2.2.4](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration), [2.2.5](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-0-identity-scope#22-scope-declaration)*

<details data-kind="rationale">
<summary>Why name what the community must not touch?</summary>

An unstated boundary is no boundary at all. Explicit out-of-scope items protect members from the community reaching into their private lives and finances, and protect external parties from the community presuming authority over their affairs. If it isn't named here, the default rule of "not in-scope means out of scope" still applies — but naming the big ones removes any room for argument.

</details>

<details data-kind="instructions">
<summary>How to fill this in</summary>

List the most important boundaries: things people might assume are in scope but aren't. Personal finances, private relationships, third-party infrastructure, external projects, etc.

</details>

1. _<Out-of-scope item 1, e.g. personal income and private finances of members.>_
2. _<Out-of-scope item 2, e.g. private relationships and personal living arrangements (except where Layer 4 safety-critical conditions apply).>_
3. _<Out-of-scope item 3, e.g. underlying server infrastructure and third-party service contracts.>_
4. _<Out-of-scope item 4.>_

---

## Ratification Record

- **Adopted:** <YYYY-MM-DD>
- **Decision type:** Constitutional
- **Version:** <version>
- **Decision record:** <link to decision record>