Fruit Haven

Layer 5 · Operations

Meeting Template: Operations

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

Meeting Type: Operations

RCOS definition7.2.1, 7.2.2, 7.2.3, 7.2.4, 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.2.4 Meeting load MUST be bounded, monitored, and reviewable as defined in Section 7.4.
  • 7.6.4 Meeting Templates MUST define, at minimum:

Read 7.2 Meeting System in the RCOS spec ↗

Why define scope, quorum, and limits up front?
A meeting without a declared decision scope will eventually be used to decide things it shouldn’t. Naming the purpose, scope, quorum, duration, and facilitator is what keeps a recurring meeting from drifting into a shadow authority.
  • Purpose: Review active work, coordinate tasks, surface blockers, and make operational decisions
  • Decision scope: Operational decisions only — cannot make Strategic or Constitutional decisions
  • Required participants: All Full Members invited; minimum quorum: Facilitator + at least one other Full Member
  • Optional participants: Trial Members or Applicants may be invited to specific agenda items by the Facilitator
  • Cadence: Weekly
  • Duration limit: 90 minutes maximum
  • Facilitation: Facilitator role holder; any Full Member may step in if the Facilitator is absent

Agenda Structure

Why a fixed agenda shape?
A consistent agenda reduces the facilitation load, makes it easier for members to prepare, and ensures check-in, review, and next actions always happen — not just when someone remembers to include them.
  1. Check-in (5 min) — one word or sentence from each participant
  2. Review last actions (10 min) — what was committed at the last meeting; what was completed, what is outstanding
  3. Role and domain updates (30 min) — brief update from each active role holder; what’s in progress, what’s needed
  4. Active agenda items (30 min) — items submitted in advance; Facilitator prioritises
  5. Operational decisions (10 min) — any decisions to make or record within Operational scope
  6. Next actions and owners (10 min) — explicit owners and timelines for all open actions
  7. Check-out (5 min) — optional; one word or sentence from each participant

Notes and Records

  • Date:
  • Facilitator:
  • Attendees:
  • Notes: [Summary posted to Discord after the meeting]

Decision Record (if applicable)

  • Decision type: Operational
  • Authority: [Role holder per Decision Matrix]
  • Mechanism / threshold: Delegated authority
  • Outcome: [What was decided]
  • Effective date:
  • Filed to: Brief note in Discord by the relevant role holder

← Back to Operations