Governance

Future proposals

Ideas and deferred decisions that are not yet technically feasible, not yet prioritised, or intentionally set aside for a later phase. Items here are candidates for future governance proposals once the conditions for implementation are met.

Priorities: High — address soon; Medium — important but not urgent; Low — nice to have.

High Priority

Treasury spending thresholds

  • Context: EcoHubs currently has no community funds — all expenses are covered by the founding member. The delegated Admin spending limit is set to €0, meaning all expenditure requires a Full Member vote. Once community funding exists (grants, partnerships, etc.), explicit spending thresholds must be adopted.
  • Trigger: When EcoHubs receives its first community funds
  • Proposed action: Strategic proposal to define: delegated Admin limit, strategic vote threshold, treasury transparency reporting cadence
  • Layers affected: Layer 2 (Decision Matrix), Layer 3 (Treasury Ruleset)
  • Context: The current system uses simple majority Snapshot voting for Strategic decisions. A future upgrade would move to consent-based decision-making — a proposal passes if no Full Member raises a reasoned objection within the deliberation period, without requiring an active vote.
  • Blocker: Requires tooling that supports consent-based voting or a modified Snapshot workflow
  • Layers affected: Layer 2 (Decision Matrix, Governance Protocol)

Medium Priority

ECO accumulation limits and decay

  • Context: ECO currently has no expiration, decay, or hard cap. As ECO gains more utility (unlocking permissions, future features), uncapped accumulation could create informal power imbalances. A decay or expiration mechanism would keep ECO meaningful as a contribution signal.
  • Trigger: When ECO utility expands beyond Puckstack permissions, or when accumulation disparities become visible
  • Layers affected: Layer 3 (Internal Economy Protocol — Internal Units, Accumulation Constraints)

Suspended Member state

  • Context: A Suspended membership state was discussed during the Layer 1 definition process. It would allow members to temporarily pause their membership (e.g. due to illness, life events, or a conflict under review in Layer 4) without fully exiting, with a generous duration cap of up to 12 months renewable once.
  • Blocker: ecohubsOS currently has no technical differentiation between Full Member and Suspended Member — Discord permissions, voting eligibility, and platform access would all need to support a distinct suspended state.
  • Proposed rights during suspension: Access to public Discord channels and public calls (listener); access to personal ecohubsOS profile; right to request reinstatement at any time.
  • Proposed obligations: None during suspension; adhere to Layer 0 identity constraints.
  • Layers affected: Layer 1 (Membership State Registry, Membership Agreement, Exit & Separation Protocol)

Low Priority

Nothing yet.