Fruit Haven

Layer 5 · Operations

2 Meeting Template: Governance

  • Layer: 5 — Operations & Coordination
  • Status: Stub — not yet adopted
  • RCOS reference: §7.2, §7.6

Meeting Type: Governance

RCOS definition7.2.1, 7.2.2, 7.2.3, 7.6.4
  • 7.2.1 The community MUST define explicit meeting types sufficient to support:
  • 7.2.2 Each meeting type MUST define, at minimum:
  • 7.2.3 Meetings MUST NOT exceed their declared decision scope or bypass authority boundaries defined in Layer 2.
  • 7.6.4 Meeting Templates MUST define, at minimum:

Read 7.2 Meeting System in the RCOS spec ↗

Why separate deliberation from the binding decision?
If a meeting can both discuss and decide, whoever is in the room that day gets to decide — regardless of quorum or authority rules. Keeping deliberation separate from the Community Meeting vote preserves the integrity of the Decision Matrix and ensures absent members still get a vote.
  • Purpose: Deliberate on an active proposal during its deliberation period, ahead of or alongside the Community Meeting vote
  • Decision scope: Deliberation only — the binding decision is made via Community Meeting vote per the Decision Matrix; no governance decisions are made in the meeting itself
  • Required participants: All Full Members invited; proposer must be present
  • Optional participants: Applicants and Trial Members may observe at the Facilitator’s discretion
  • Cadence: As needed during deliberation periods
  • Duration limit:
  • Facilitation: Facilitator role holder

Agenda Structure

Why separate clarifying questions from deliberation?
Mixing factual questions with advocacy is how discussions go sideways — people argue past each other before they’ve even agreed on what the proposal says. Splitting clarification from deliberation keeps the conversation grounded in the proposal itself.
  1. Check-in — one word or sentence from each participant
  2. Proposal summary — proposer presents the proposal: what it changes, why, and what the alternatives considered were
  3. Clarifying questions — factual questions only; no advocacy yet; Facilitator manages the queue
  4. Open deliberation — members share perspectives, concerns, and support; Facilitator ensures all voices are heard
  5. Summary of positions and next steps — Facilitator summarises key points of agreement and disagreement; confirms Community Meeting vote timeline

Notes and Records

  • Date:
  • Facilitator:
  • Attendees:
  • Notes:

Decision Record

  • Proposal reference: [Link to proposal file in proposals/]
  • Decision type: Strategic / Constitutional
  • Authority: Full Members (collective)
  • Mechanism / threshold: Community Meeting — per Decision Matrix
  • Outcome: Passed / Rejected / Tabled
  • Vote count (if applicable):
  • Effective date:

← Back to Operations