Layer 5
Operations
How the community runs day-to-day. Roles, manual, and meeting templates.
Layer 5
How the community runs day-to-day. Roles, manual, and meeting templates.
Critical processes must be documented such that continuity does not depend on knowledge held by specific individuals.
→All ongoing responsibilities must be assigned to explicit, named roles. No ongoing responsibility may exist without an explicit role entry here.
→The weekly coordination meeting. Used to review active work, surface blockers, hand off between roles, and make day-to-day operational decisions. The only binding decisions that…
→Used during the deliberation period of an active proposal, before or alongside the Snapshot vote. The meeting itself does not make binding decisions — it is a structured space for…
→Used when cross-role work needs explicit synchronization — dependencies, handoffs, or competing priorities. Held monthly or triggered when a blocker spans more than one role. Not…
→The quarterly retrospective. Used to look back across the period, identify what worked and what didn't, capture learnings in the Learning Log (Layer 6), and surface items that…
→The facilitated session template for Conflict Resolution Ladder Steps 2–4. Triggered by a conflict intake, not scheduled. Fully confidential — records are restricted to parties…
→