Fruit Haven

Layer 5 · Operations

Meeting Template: Coordination & Alignment

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

Meeting Type: Coordination & Alignment

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 bound scope and participants for this meeting?
Without a declared scope, a coordination meeting becomes a second Operations meeting — doubling the meeting load for no gain. Keeping it focused on cross-role synchronization, and limiting required participants to those with active initiatives, preserves its purpose.
  • Purpose: Synchronize work across roles and initiatives; surface dependencies and blockers; align on priorities
  • Decision scope: Operational decisions only — cannot make Strategic or Constitutional decisions
  • Required participants: Role holders with active initiatives
  • Optional participants: All Full Members welcome
  • Cadence: Monthly or as needed when cross-role coordination is required
  • Duration limit: 60 minutes maximum
  • Facilitation: Facilitator role holder; may be facilitated by any role holder if the Facilitator is unavailable

Agenda Structure

Why front-load status and blockers?
Most cross-role friction shows up as either a missing update or a blocker nobody named. Front-loading both, before discussing next steps, makes the real coordination problems visible instead of leaving them to emerge indirectly.
  1. Check-in (5 min) — one word or sentence from each participant
  2. Initiative status updates (30 min) — each role holder briefly covers: what’s in progress, what’s completed since last time, what’s needed from other roles
  3. Blockers and dependencies (15 min) — flag anything stalling progress across role boundaries; agree on owners and timelines for resolution
  4. Next steps (10 min) — confirm priorities and next actions with explicit owners

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:

← Back to Operations