Update curriculum source files to current versions

9 session pages and 10 PS Guide markdown files for the Baby Ghosts
cooperative foundations curriculum. Import script creates documents in
Outline wiki with cross-links between paired session/PS Guide pages.

.gitignore

@@ -23,6 +23,9 @@ conflict-files-obsidian-git.md
 .env.*
 !.env.example
 
+# Root markdown files (local only)
+/*.md
+
 # Project docs (local only)
 /docs
 /migration

content/curriculum/PS Guides/0-kickoff-onboarding.md

@@ -0,0 +1,42 @@
+# 0: Kickoff & Onboarding
+## Pre-session
+
+- Review Session 0 agenda and your intro talking points
+- Be ready to introduce yourself and your studio's journey
+
+## **What happens in session**
+
+This is the full cohort's orientation to the program. Participants do introductions, learn about the program structure, build initial community agreements, and get the Power Flower homework.
+
+
+:::info
+A theme we want to emphasize (based on feedback from Cohort 5) is: **"friction is part of the work."** It's to be expected, and is not something to fear or avoid. 
+
+:::
+
+
+### :eyes: **Your role during session**
+
+- You're introduced and matched with your studio
+- Observe your studio during introductions – who talks, who doesn't, what pain points do they talk about?
+- Participate in community agreements drafting – you are ***part of the community!***
+
+
+### **👆Your role after session**
+
+- Connect and chat with your studio in their Slack channel(s)
+- Make sure they understand the Power Flower homework (especially that it is a private, individual reflection, and no one else will see it unless they want to share)
+- Note any first impressions to share at the PS check-in
+
+
+### :triangular_flag_on_post: **Red flags to watch for**
+
+- One person from the studio dominates introductions or positions themselves as the main character
+- Team members who seem checked out already
+
+
+### :hammer_and_wrench: **Tools introduced**
+
+- Power Flower (homework, private)
+- __[Community agreements](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Policies/Loving+Justice)__ (Miro, collective)
+- __[Loving Justice](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Policies/Loving+Justice)__ framework

content/curriculum/PS Guides/1-coop-principles-power.md

@@ -0,0 +1,142 @@
+# 1: Coop Principles & Power
+
+## **What happens in session**
+
+In this session, we cover cooperative history and lineages, crediting Global South, Indigenous, Black, women's traditions, not just Rochdale. We also review the 7 ICA Principles.
+
+The theme is *moving from principles to personal values*.
+
+
+:::tip
+**Homework assigned:** individual journaling, team values map (with PS), and individual prep for The Talk (Session 2).
+
+:::
+
+
+### :eyes: **Your role during session**
+
+- Observe small group activity (cooperative lineage sharing) – note whose stories are shared
+- Listen for how studios talk about values – vague or specific?
+
+
+## **This week's Studio Support Meeting: Values Mapping**
+
+### **📚 Materials**
+
+- Studio Miro board with Values Mapping template
+- 7 Principles reference
+
+
+### **👆 Before the session**
+
+- Confirm everyone completed their individual journaling (Session 1 homework)
+- Ensure the studio Miro board has the template
+- Have the 7 Principles visible (on the board or screen-shared)
+
+
+### **🌊 Session flow**
+
+#### **Check-in (5 min)**
+
+Individual sharing (15-20 min) – Each person shares 3-5 values from their individual reflection.
+
+Prompts:
+
+- "What values came up when you did the journaling?"
+- "You don't need to explain or justify."
+
+As they share: each person adds values to the Miro board (stickies in their colour/section). No discussion – just capture.
+
+Watch for: Someone dominating or going first every time; someone staying quiet – invite them in gently; values that sound the same but might mean different things to different people.
+
+
+#### **Noticing patterns (10-15 min)**
+
+Look at the board together.
+
+Prompts:
+
+- "What do you notice?"
+- "Where do you see overlap?"
+- "Any surprises?"
+- "Are there values that seem similar but might mean different things to different people?"
+
+
+> Example to offer: "Transparency" – does it mean open documents? Open conversations? Both? Neither? What exactly is meant?
+
+
+**Connecting to the 7 Principles (10 min)**
+
+Look at the ICA principles together.
+
+**Prompts**:
+
+- "Do you see connections between your values and these principles?"
+- "Draw lines or group things if it helps."
+    – This can be loose – don't let them fixate on making a beautiful diagram. The point is seeing that their values connect to a larger cooperative tradition.
+
+
+#### **To bring back to Session 2 (5 min)**
+
+**Prompts**:
+
+- "What's one thing you learned about where your team aligns or diverges?"
+	- You'll share this in Session 2 – doesn't need to be polished. Have someone write it down or capture it on the board.
+
+
+#### **Community agreements contribution (5 min)**
+
+"Based on this conversation, are there 1-2 values you'd propose adding to the cohort community agreements?" Capture these to bring back to the full group.
+
+
+### :star: **Tips**
+
+
+If someone is dominating:
+
+- "Let's hear from someone who hasn't shared yet."
+
+
+If no one talks… awkward silence:
+
+- "Take a minute to look at the board silently. What stands out?"
+
+
+If tension emerges:
+
+- "Sounds like there are some different perspectives here. That's useful but we don't need to resolve it today."
+
+
+If they want to debate definitions:
+
+- "It's okay to mean different things. The goal is simply to notice where you might need to clarify later."
+
+
+If time runs short:
+
+- Prioritize steps 2-3 (sharing and noticing). The principles connection and agreements contribution can be done async if needed.
+
+
+### **🏁After the session**
+
+- Note any tensions/surprises for your PS check-in
+- Remind the team to bring their learnings to Session 2
+
+### **👉 Also this week**
+
+#### **Make sure they're prepping for The Talk**
+
+Session 2 homework includes individual prep on four topics: financial reality, time/availability, skills/contributions, decision-making styles. 
+
+
+:::warning
+They need to *write their answers down* before Session 2. Check that they're doing this!
+
+:::
+
+
+### :triangular_flag_on_post: **Red flags to watch for**
+
+- A studio that can't name any values beyond "we want to make good games" – don't we all! Too vague.
+- One person speaking for the group about "our" values
+- Values that are all abstract with no grounding in practice

content/curriculum/PS Guides/2-shared-purpose-alignment.md

@@ -0,0 +1,190 @@
+# 2: Shared Purpose & Alignment
+
+## **What happens in session**
+
+This session, we talk about the challenges of *aligning on the studio's purpose*.
+
+We go over common pitfalls – vague goals like "we all just want to make good games" and assuming shared politics means shared work values. We do four rounds of The Talk, asking detailed individual questions about financial reality, time/availability, skills/contributions, and decision-making styles. Studios practice this in their channels with the Peer Support present.
+
+### :eyes: **Your role during session**
+
+***This is a big one.*** You're facilitating The Talk in your studio's breakout room (aka their project or studio channel). Here are some things to watch for:
+
+
+Financial reality:
+
+- People minimizing their own needs
+- Wide gaps in financial situations not being acknowledged
+- Someone going quiet
+
+
+Time/availability:
+
+- Vague answers
+- Someone over committing to match others
+
+
+Skills/contributions:
+
+- People only naming strengths and not gaps
+- Assumptions about roles based on past
+- Someone taking on the hard or tedious stuff by default
+
+
+Decision-making:
+
+- Very different styles that could clash (fast decider vs. slow processor)
+- Someone who goes along to avoid conflict
+- Past conflicts referenced passively
+
+
+### :triangular_ruler: **Format**
+
+Each person answers in turn (2 min each), use the Miro timer, brief open discussion after everyone answers, then move to next round.
+
+The goal isn't to solve everything today, just to get the conversation started!
+
+## **This week's Studio Support Meeting: Continuing The Talk**
+
+**Materials:** Notes from Session 2 activity, participants' original prep from Session 1
+
+### :world_map: **Context**
+
+In Session 2, studios practiced The Talk – four rounds covering financial reality, time/availability, skills/contributions, and decision-making styles. They started these conversations but didn't finish them (this is the intention). During this Studio Support Meeting, help them go deeper: Create space to continue conversations that got cut short or stayed shallow, draw out what went unsaid, help the team notice patterns.
+
+This is an ongoing practice!
+
+### :ocean: **Session flow**
+
+#### **Check-in (5 min)**
+
+"How did The Talk feel for you? Anything still sitting with you from Session 2?" Let each person respond briefly. Listen for tensions, moments of relief, unfinished ideas.
+
+#### **Go deeper on one round (20-25 min)**
+
+"Which round felt most unfinished or brought up the most tension?" Revisit the questions in the round they choose, but this time, push past the first answer.
+
+
+***For financial reality:***
+
+
+1. What would change for you if the studio couldn't pay you anything for six months?
+2. Are you trying not to seem demanding, and not sharing your true needs?
+3. Are there differences in monetary needs that create (a sense of) unbalanced power dynamics?
+
+
+***For time and availability:***
+
+
+4. How many hours per week can you reliably, actually commit – a hard number.
+5. What's something that would cause you to miss a deadline? How would you want to handle that as a team?
+6. Are you building around one person's availability? Intentionally?
+
+
+***For skills and contributions:***
+
+
+7. What happens if no one does the "dreaded task"?
+8. When you're overwhelmed, do you want people to check in or give you space? Does the team know that about you?
+9. Is anyone doing work that isn't visible or acknowledged?
+
+
+***For decision-making:***
+
+
+10. What happens if you disagree about something, but don't say anything?
+11. Has there been a decision in this group where you felt unheard?
+12. When you're under pressure, do you speed up or slow down? Do these styles clash between members?
+
+
+#### **Draw out the unsaid (15 min)**
+
+
+:::warning
+***This could be hard.*** "Was there anything you wanted to say in Session 2 but didn't?"
+
+:::
+
+Give silence and let it be awkward. *You really need to relish the awkwardness.* Let folks build up courage to speak up. If nothing comes up, at least you've created an opening for later.
+
+- Is there a question you wish someone had asked you?
+- Is there something you noticed about a teammate's answer that you're still thinking about?
+- Is there an elephant in the room?
+
+If something big comes up: help them decide – "Is this something you want to keep talking about now, or table for later?"
+
+
+### Close and next steps (5 min)
+
+"What's one thing you want to carry forward from this conversation?"
+
+Remind them: these conversations don't end here; tension is interesting information, not failure; they can bring things back to future PS sessions.
+
+**Nudge them on their Session 2 homework:** writing down tension points and unsaid questions. Check that they're doing this – we need this to build on later.
+
+## :triangular_flag_on_post:**Red flags**
+
+- One person's needs consistently minimized (by themselves or others)
+- Financial gaps with no acknowledgment of how they affect power
+- A founder or initiator whose preferences are treated as default
+- Someone checked out or going along without engaging
+- A topic the group keeps avoiding
+- Stuck or clearly in conflict
+
+Note these for your PS check-in or message in the channel.
+
+## :point_right: **Also this week: Scale and Pace**
+
+**Duration:** 15-20 minutes (can be folded into the same meeting as Continuing The Talk, or done as a separate short check-in)
+
+**Context:** Session 2 homework asks each person to individually reflect on where they see the studio in 1/3/5 years and what their revenue model might look like. This is just a conversation starter. You're helping them notice where their assumptions about the studio's future align or diverge.
+
+
+**Before the conversation:**
+
+- Confirm everyone has done some thinking on this (even loosely). If they haven't, give them 5 minutes of quiet writing time before you start.
+
+
+**How to facilitate:**
+
+Start with a round: Each person shares one thing about where they see the studio. Keep it brief – you're listening for gaps, not building a business plan.
+
+
+Prompts to draw out differences:
+
+- "When you picture the studio in three years, how many people are on the team?"
+- "Are you imagining one game, or multiple projects?"
+- "What does 'success' look like for you personally – not the studio, *you*?"
+- "Is this your full-time thing, or alongside other work?"
+
+
+Then ground it:
+
+- "Who are your players? Do you know?"
+- "What's your revenue model – game sales, services, grants, a mix?"
+- "Can that sustain you? For how long?"
+- "What happens if the game takes twice as long as you think?"
+
+
+**What you're listening for:**
+
+- Major mismatches in ambition (one person wants a 20-person studio, another wants a 3-person collective)
+- Revenue model assumptions that haven't been tested or discussed ("we'll just get a publisher")
+- Someone who hasn't thought about this at all
+- Scale assumptions that don't match the team's actual capacity
+- Different definitions of sustainability (covering rent vs. building wealth vs. just making a game)
+
+
+**What you're not doing:** Judging their plans or telling them what's realistic. You're helping them see whether they're actually talking about the same studio.
+
+
+:::tip
+**Tip:** **If you notice a big gap** – say, one person assumes this is a side project and another has quit their job for it – name it gently. "I'm noticing you might be picturing different scales here. Is that something you've talked about?" This is the kind of divergence that festers if it stays unspoken.
+
+:::
+
+
+**After the conversation:**
+
+- Note any major alignment gaps for your PS check-in
+- They'll keep returning to scale and pace throughout the program – this is just the first pass

content/curriculum/PS Guides/3-actionable-values-impact.md

@@ -0,0 +1,156 @@
+# 3: Actionable Values and Impact
+
+## Pre-session
+
+If you are the presenting PS for this session, prepare a **10-minute** case study from your studio covering:
+
+- How you arrived at your current values (what process did you use? what changed through iteration?)
+- One example of values guiding a real decision – especially a hard one
+- Where you've seen a gap between stated values and actual practice, and what you did about it
+
+Show the messy stuff. Participants need to see that this work is ongoing, not a one-time exercise.
+
+## **What happens in session**
+
+Studios move from identifying values to making them operational. The session introduces two tools: the Why/What/How framework (turning values into concrete practices) and Layers of Effect (mapping ripple effects of decisions). A Peer Support presenter shares a case study from their own studio. Studios work through scenarios using values-first thinking and identify a decision to run through the tools with their PS this week.
+
+### :eyes: **Your role during session**
+
+- If presenting: Deliver your case study. Be honest about what didn't work and what you're still figuring out.
+- Observe your studio during the scenario exercise – who applies values first vs. jumping to solutions?
+- Note whether studios can connect their Session 1 values to the tools, or if values are still too vague to be actionable.
+
+
+### 👆 **Your role after session**
+
+- Confirm everyone understood the Why/What/How framework and the Layers of Effect template
+- Make sure the Miro templates (Why/What/How and Layers of Effect) are on your studio's board
+- Note which decision they chose for the homework activity
+
+
+## **This week's Studio Support Meeting: Why/What/How + Layers of Effect**
+
+### **📚 Materials**
+
+- Studio Miro board with Why/What/How template
+- Studio Miro board with [Layers of Effect template](https://miro.com/templates/layers-effect-template/)
+- The studio's values map from Session 1
+
+
+### **👆 Before the session**
+
+- Confirm the Miro templates are set up and accessible
+- Review the studio's values map – pick 1-2 values that seem ripe for the Why/What/How exercise (have a suggestion ready in case the team gets stuck)
+- Know which decision they identified at the end of Session 3 for the Layers of Effect exercise
+
+
+### **🌊 Session flow**
+
+#### **Check-in (5 min)**
+
+"How did the scenario exercise land for you? Was it easy or hard to start with values before jumping to solutions?"
+
+Let each person respond briefly. Listen for whether they found the tools useful or abstract.
+
+
+#### **Why/What/How deep dive (20-25 min)**
+
+Pick one value from the studio's values map together and work through the full framework.
+
+**Step 1: WHY (5-7 min)**
+
+"Why does this value matter to your studio? What's at stake if you don't practice it?"
+
+Prompts if they get stuck:
+
+- "What would go wrong if you dropped this value tomorrow?"
+- "Who is affected if this value isn't practiced?"
+
+**Step 2: WHAT (5-7 min)**
+
+"What does practicing this value actually look like? What are you committing to?"
+
+Push for specificity:
+
+- "If a new member joined next month, how would they know you practice this value?"
+- "'We value transparency' – what does that mean concretely? Open finances? Open conversations? Open documents?"
+
+**Step 3: HOW (5-7 min)**
+
+"How will you actually do this? What specific activities, rituals, or outputs?"
+
+This is where it gets real:
+
+- "How often? Who's responsible? Where does it live?"
+- "What's the minimum viable version you could start this week?"
+
+Capture everything on the Miro board.
+
+
+#### **Layers of Effect practice (15-20 min)**
+
+Use the decision they identified in Session 3. Walk through the three rings together.
+
+:::tip
+**Parallel framework for context:** Neil Postman's "Seven Questions for any new technology" maps closely to Layers of Effect. If a studio is struggling with the concentric rings framing, try Postman's questions as an alternate way in: (1) What problem does this solve? (2) Whose problem is it? (3) What new problems does solving it create? (4) Who is most impacted? (5) What changes in language? (6) What shifts in power? (7) What unintended uses might emerge?
+:::
+
+**Primary effects (5 min):** "What are the direct, immediate impacts of this decision?"
+
+- Who gains? Who pays? Who's invisible but affected?
+
+**Secondary effects (5 min):** "What are the known but less obvious impacts?"
+
+- What dependencies or new risks are you introducing?
+
+**Tertiary effects (5 min):** "What unforeseen consequences might emerge over time?"
+
+- What standards could this establish? What shifts over years?
+
+Use yellow stickies for opportunities/benefits and red for risks/costs. These might be connected – a benefit in one layer can create a risk in another.
+
+**Debrief (5 min):**
+
+- "Did mapping this change how you think about the decision?"
+- "Did your values hold up, or did you notice a gap between intention and effect?"
+
+
+#### **Close and next steps (5 min)**
+
+- "How often should you revisit your values and check whether your effects match your intentions?"
+- Encourage them to make this a recurring practice, not a one-time exercise
+
+
+### :star: **Tips**
+
+If the Why/What/How stays vague:
+
+- "Can you make that even more specific? What would someone actually *see* you doing?"
+
+If they rush through Layers of Effect:
+
+- "Slow down at tertiary. The unforeseen stuff is where the most important learning happens."
+
+If they only see positive effects:
+
+- "Every decision has costs. Who bears them? Who's invisible here?"
+
+If one person dominates the values conversation:
+
+- "Let's hear from everyone – whose experience of this value is different?"
+
+
+### **🏁 After the session**
+
+- Note whether the studio can translate values into practices or if they're still stuck at the abstract level
+- Note any gaps between stated values and emerging practices – these will come up again
+- Remind them to discuss as a studio: how often should you revisit values and check your effects?
+
+
+## :triangular_flag_on_post: **Red flags to watch for**
+
+- Values that are all "why" with no "what" or "how" – inspiration without practice
+- A studio that can't see any negative effects of their decisions – lack of critical thinking or avoidance
+- One person defining "our" values without challenge from the group
+- Tools treated as a box-checking exercise rather than genuine reflection
+- "We already know our values" without being able to articulate practices

content/curriculum/PS Guides/4-decision-making-in-practice.md

@@ -0,0 +1,150 @@
+# 4: Decision-Making in Practice
+
+## **What happens in session**
+
+Studios explore cooperative decision-making frameworks (consensus, consent, majority, delegation, random chance). They practice identifying who gets to raise issues, work through decision-making steps, and discuss handling dissent. The session also covers meetings (roles, facilitation, rotating responsibilities) and the "genius trap." Studios do a facilitation rotation practice in groups of three. The Informal Hierarchy Check-In is introduced as an ongoing tool.
+
+
+:::tip
+**Homework assigned:** practice one decision-making framework on a real decision, map current role distribution, complete the Informal Hierarchy Check-In as a studio, and notice where decisions happen this week.
+
+:::
+
+
+### :eyes: **Your role during session**
+
+- Observe the facilitation rotation activity – note how your studio members handle facilitating, participating, and observing
+- Listen for how they talk about where decisions currently happen (meetings? DMs? default to one person?)
+- Note whether anyone identifies informal hierarchy patterns during the journaling activity
+
+
+### 👆 **Your role after session**
+
+- Make sure your studio understands the Informal Hierarchy Check-In questions and plans to work through them together
+- Confirm they've chosen which decision-making framework to practice this week
+- Check that they understand the difference between consensus and consent – this trips people up
+
+
+## **This week's Studio Support Meeting: Decision-Making Practice + Informal Hierarchy Check-In**
+
+### **📚 Materials**
+
+- Informal Hierarchy Check-In questions (from session)
+- Decision-making frameworks reference (consensus, consent, majority, delegation)
+- The studio's notes from the facilitation rotation activity
+
+
+### **👆 Before the session**
+
+- Know which decision-making framework the studio chose to practice
+- Have a small, real decision ready in case the studio can't think of one (e.g., "What should your next team social activity be?" or "How should you structure your next sprint?")
+- Review the 5 Informal Hierarchy Check-In questions so you can facilitate them smoothly
+
+
+### **🌊 Session flow**
+
+#### **Check-in (5 min)**
+
+"What did you notice in the facilitation rotation? What was harder than expected – facilitating, participating, or observing?"
+
+#### **Practice a decision-making framework (20-25 min)**
+
+Help the studio work through a real decision using their chosen framework.
+
+**Set up (3 min):**
+
+- Name the decision clearly. Write it down where everyone can see it.
+- Name the framework you're using – "We're going to try consent on this."
+- Clarify: who is affected by this decision? Does everyone here need to be part of it?
+
+**Work through the decision-making steps (15-20 min):**
+
+1. Understand the context – what's happening? What do people feel about it?
+2. Identify the underlying need – what are we actually trying to address?
+3. Generate options – encourage weird ideas. Notice who contributes.
+4. Check alignment with values – how do these options fit with who you want to be?
+5. Evaluate consequences – who benefits, who's affected, trade-offs?
+6. Decide using the framework – name the method before you begin.
+7. Before finalizing: "Does anyone have concerns they haven't voiced? Is anyone agreeing just to move on?"
+8. Clarify implementation – who does what? When do you check back?
+
+**Debrief (5 min):**
+
+- "How did that feel compared to how you usually make decisions?"
+- "What was different about naming the framework first?"
+- "Did anyone notice moments where old patterns kicked in?"
+
+
+#### **Informal Hierarchy Check-In (15-20 min)**
+
+Work through the five questions together. Go one at a time.
+
+1. **Who spoke most in our last meeting?**
+2. **Whose idea did we go with by default?**
+3. **Who knows how to do [X] that no one else knows?**
+4. **What happened last time someone disagreed?**
+5. **Whose schedule shapes our meeting times?**
+
+Prompts to keep it exploratory, not accusatory:
+
+- "No guilt here – we're just noticing."
+- "These patterns aren't problems yet. But under pressure, they become cracks."
+- "What would you want to change? What's actually fine?"
+
+Capture observations – they'll bring these to Session 5.
+
+
+#### **Close (5 min)**
+
+- "What's one pattern you noticed that you want to keep an eye on?"
+- Remind them to notice where decisions happen this week (in meetings? DMs? Slack? who's present?)
+
+
+### 👉 **Also this week**
+
+#### **Map your current role distribution**
+
+This can be done async or as part of the PS meeting if there's time. The question is simple: for each role/responsibility in the studio, where did it come from – explicit decision or implicit default?
+
+Prompts:
+
+- "Who handles finances? Was that decided or did it just happen?"
+- "Who schedules meetings? Who takes notes? Who answers external emails?"
+- "Are there roles no one officially has but someone 'just does'?"
+
+This feeds directly into Session 5's governance work.
+
+
+### :star: **Tips**
+
+If the decision-making practice feels artificial:
+
+- "The point is to *notice* the process. How you decide matters as much as what you decide."
+
+If one person dominates the decision:
+
+- "I noticed [name] spoke first and longest. Can we try a round where everyone shares before discussion?"
+
+If no one disagrees:
+
+- "That was quick! Is everyone actually aligned, or is someone going along to keep things moving?" (This is a direct reference to the dissent section from the session.)
+
+If someone gets defensive:
+
+- "It's okay – noticing patterns is the hardest part. You don't need to fix anything today."
+
+
+### **🏁 After the session**
+
+- Note which patterns came up in the Informal Hierarchy Check-In – especially anything the studio seemed to avoid discussing
+- Note how the decision-making practice went – did they actually use the framework or fall back into old patterns?
+- Bring observations to your PS check-in
+
+
+## :triangular_flag_on_post: **Red flags to watch for**
+
+- A studio that "decides" everything by default to one person and calls it delegation
+- Someone consistently going along without engaging – "I'm fine with whatever"
+- Resistance to the hierarchy check-in – "we don't have hierarchy, we're all equal" (it's insidious)
+- Decisions happening outside the room (in DMs between two people) and being presented as done
+- The same person always facilitating, taking notes, or scheduling

content/curriculum/PS Guides/5-coop-structures-governance.md

@@ -0,0 +1,144 @@
+# 5: Coop Structures and Governance
+
+## Pre-session
+
+If you are the presenting PS for this session, prep a **15-20 minute** case study from your studio covering:
+
+- How your studio makes decisions now
+- What you tried that didn't work
+- One example of governance helping resolve a real issue
+
+## **What happens in session**
+
+Studios learn about:
+- legal structures (sole prop, partnership, corporation, worker coop)
+- governance models (collective governance, advice process, sociocratic circles, board + membership, DisCOs)
+- member management (adding, departing, removing members)
+
+A PS presenter shares a 15-20 minute case study on their studio's governance journey. We also introduce Community Rule as a tool for documenting governance in plain language. We focus on *making governance visible*, designing structures from the patterns noticed in Session 4, and distinguishing between governance practice and legal incorporation.
+
+### :eyes: **Your role during session**
+
+- If presenting: deliver your case study
+- Observe how your studio responds to the governance models – what resonates? What causes confusion or resistance?
+- Listen for whether they connect their Session 4 Informal Hierarchy Check-In observations to governance design choices
+- Note how they react to the member removal discussion. It's an uncomfortable topic.
+
+
+### 👆 **Your role after session**
+
+- Make sure your studio has access to [Community Rule](https://communityrule.info/)
+- Confirm they understand the homework: start a Community Rule draft with you, discuss financial sustainability, and do a personal reflection on financial access
+- Note which governance model(s) they're gravitating toward
+
+
+## **This week's Studio Support Meeting: Community Rule Drafting**
+
+### **📚 Materials**
+
+- [Community Rule](https://communityrule.info/) tool
+- Studio's Informal Hierarchy Check-In observations from Session 4
+- Notes on which governance model(s) interested them
+
+
+### :world_map: **Context**
+
+This is a working session. You're helping the studio start documenting their governance in plain language using Community Rule. They don't need to finish – the goal is to surface where they already have answers vs. where they need more conversation. This will be a living document.
+
+
+### **👆 Before the session**
+
+- Familiarize yourself with the Community Rule interface and fields
+- Review the studio's Informal Hierarchy Check-In observations
+- Have the governance models overview handy (collective governance, advice process, circles, board + membership) in case they need a refresher
+
+
+### **🌊 Session flow**
+
+#### **Check-in (5 min)**
+
+"What governance model stuck with you from the session? Did anything click, or feel wrong?"
+
+
+#### **Community Rule walkthrough (10 min)**
+
+Open the tool together. Community Rule works as a modular builder – you assemble your governance from pre-made or custom building blocks.
+
+Start with the basics: Name your studio and write a short summary of its structure.
+
+Then explore the module library together. There are four categories:
+
+- **Culture** – values, norms, purpose, solidarity, diversity
+- **Decision** – how decisions get made (lazy consensus, do-ocracy, vote, ranked choice, etc.)
+- **Process** – how policies are implemented and evolve (accountability process, delegation, transparency, dissolution, exclusion, etc.)
+- **Structure** – roles and internal entities (board, council, membership, ownership, roles, committee, etc.)
+
+Drag in the modules that feel relevant. Each one can be configured with key-value pairs – for example, a "Membership" module might have configuration like "Eligibility: active worker-owners who have completed a 3-month trial period." You can also create custom modules for anything the library doesn't cover.
+
+Don't try to build everything at once. Start by browsing the categories and noticing which modules the studio can configure easily vs. which ones lead to blank stares.
+
+Prompts:
+
+- "Which of these are you already doing without naming it?"
+- "Where is there genuine disagreement or uncertainty?"
+- "What's missing from the library that's specific to how you work?"
+
+#### **Draft together (20-25 min)**
+
+Start filling in what you can. Focus on the modules where there's energy or alignment. When you hit a field where there's disagreement, note it and move on. Don't try to resolve everything today.
+
+#### **Close and gaps list (5 min)**
+
+- Make a list of areas that still need discussion
+- "What's the most important unresolved question?"
+- "Who's going to take a first pass at writing up what we decided today?"
+
+
+### 👉 **Also this week**
+
+#### **Financial sustainability conversation**
+
+Session 5 homework asks each person to reflect: *What does financial sustainability look like for you personally? What would you need from this project?*
+
+This is prep for Session 6 (Equitable Economics). Check in during the week:
+
+- "Has everyone spent some time thinking about the financial sustainability question?"
+- "And the personal reflection: what financial information have you never been allowed to see at work?"
+
+These don't need to be discussed as a studio yet – just make sure individuals are reflecting.
+
+
+### :star: **Tips**
+
+If they want to pick a governance model immediately:
+
+- "You don't have to commit today. Start with collective governance or advice process – you can add complexity as you learn what you actually need."
+
+If Community Rule feels bureaucratic:
+
+- "You're already doing governance – this just helps you name it."
+
+If they skip over membership/removal:
+
+- "This is the part that matters most when things get hard. Even a rough sketch now saves a lot of pain later."
+
+If one person is doing all the talking about governance:
+
+- "Governance designed by one person is just management with extra steps. Everyone needs to shape this."
+
+
+### **🏁 After the session**
+
+- Note where the studio has clear alignment vs. where they got stuck
+- Note any tension around membership/removal – these conversations will deepen
+- Remind them about the financial sustainability reflection for Session 6 prep
+- Bring the draft status to your PS check-in
+
+
+## :triangular_flag_on_post: **Red flags to watch for**
+
+- A studio that resists documenting anything – "we just know how we work" (exactly the problem)
+- Governance designed around one person's strengths or preferences
+- Avoiding the membership/removal conversation entirely
+- Confusing governance with incorporation – "we're not a real coop yet so we don't need this"
+- A draft that looks perfect on paper but doesn't match how the studio actually operates

content/curriculum/PS Guides/6-equitable-economics.md

@@ -0,0 +1,163 @@
+# 6: Equitable Economics
+
+## **What happens in session**
+
+This is a dense session covering revenue sources, financial transparency, compensation models (equal pay, needs-based, role-based, hybrid), profit-sharing basics, and IP ownership. Studios discuss what financial sustainability means personally, explore open-book practices, and start thinking about what "fair" compensation looks like. The session connects financial decisions to the governance structures from Session 5.
+
+
+:::tip
+**Homework assigned:** discuss financial transparency (what feels vulnerable to share?) and compensation models (what feels fair?). These conversations are prep for the PS meeting this week.
+
+:::
+
+
+### :eyes: **Your role during session**
+
+- Observe how your studio reacts to the compensation models discussion – where do they light up? Where do they tense up?
+- Listen for financial information gaps – who has financial literacy? Who doesn't?
+- Note whether anyone avoids the personal financial sustainability question
+- Watch the IP ownership discussion – this can surface unexpected disagreements, especially if someone brought existing work into the project
+
+
+### 👆 **Your role after session**
+
+- Check that everyone understands the homework and is willing to have the financial conversations
+- Note any immediate tensions about money that surfaced during the session
+- Make sure they know the tools mentioned: [CoBudget](https://cobudget.com/), [OpenCollective](https://opencollective.com/), [coop.love](https://coop.love)
+
+
+## **This week's Studio Support Meeting: Financial Transparency and Compensation**
+
+### **📚 Materials**
+
+- Compensation models reference (equal pay, needs-based, role-based, hybrid)
+- Studio's Community Rule draft from Session 5 (financial decision-making sections)
+- Revenue sources overview from the session
+
+
+### :world_map: **Context**
+
+Money is where values meet reality. This studio support meeting helps the studio have the financial conversations that most groups avoid. Your role is to create enough safety for vulnerability while pushing past surface-level comfort. These conversations don't need to reach decisions today – they need to *happen*.
+
+
+### **👆 Before the session**
+
+- Check in about whether they've started reflecting on the homework questions
+- Review the studio's governance draft – what did they decide about financial decision-making?
+- Be prepared for this session to be emotionally charged
+
+
+### **🌊 Session flow**
+
+#### **Check-in (5 min)**
+
+"The session covered a lot of ground about money. What's sitting with you? Anything surprising – or anything you're dreading talking about?"
+
+
+#### **Financial transparency (15-20 min)**
+
+Start with the personal reflection prompt from Session 5 homework:
+
+"What financial information have you never been allowed to see at work. What might have been different if you had?"
+
+Let each person share. This grounds the conversation in lived experience before it becomes abstract.
+
+Then move to the studio:
+
+**Prompts:**
+
+- "What financial information would feel vulnerable to share with your studio?"
+- "What would you need in order to feel safe sharing it?"
+- "What's the minimum level of financial transparency you'd want in your coop?"
+
+**Practical questions:**
+
+- "Who currently knows the most about the studio's finances? Is that a choice or a default?"
+- "If you were to do open books – what would that actually look like? A shared spreadsheet? Monthly summaries? Full access to accounts?"
+- "What's one step you could take this week toward more transparency?"
+
+Don't push anyone to share financial details they're not ready to. The goal is *naming the discomfort*.
+
+
+#### **Compensation models (15-20 min)**
+
+Review the four models briefly:
+
+- **Equal pay:** same rate regardless of role
+- **Needs-based:** adjusted for members' actual financial situations
+- **Role-based:** different rates for different roles
+- **Hybrid:** base rate plus adjustments
+
+**Discussion prompts:**
+
+- "What feels fair to you? Where do you notice tension between 'fair' and 'comfortable'?"
+- "What would you need to know about each other's situations to decide together?"
+- "Which model aligns best with your values?"
+
+**Dig deeper:**
+
+- "If you chose equal pay, what happens when one person is working 40 hours and another is working 15?"
+- "If you chose needs-based, who decides what counts as a 'need'?"
+- "If you chose role-based, who decides which roles are worth more – and doesn't that recreate hierarchy?"
+
+You don't need to reach a decision.
+
+
+#### **IP ownership – first pass (5-10 min)**
+
+If there's time, and only if the studio is ready:
+
+- "Who owns the game you're making together?"
+- "Has anyone brought existing work into the project? What happens to that?"
+- "What happens to IP if someone leaves?"
+
+If these questions create tension, name it: "This is the kind of conversation that gets harder the longer you wait. Notice where you're not aligned."
+
+
+#### **Close (5 min)**
+
+- "What's one financial conversation your team has been avoiding?"
+- "What's one concrete step you can take before next session?"
+- Remind them: Session 7 is about conflict – and money is often where conflict shows up first
+
+
+### :star: **Tips**
+
+If someone shuts down:
+
+- "Money stuff can be really personal. You don't have to share anything you're not ready to. But notice what you're protecting and why."
+
+If the group avoids specifics:
+
+- "Saying 'we'll figure it out later' is a to avoid financial conversations. Try to think of a specific decision to discuss today."
+
+If one person has significantly more financial literacy:
+
+- "Part of transparency is making sure everyone can participate in financial decisions. Can you explain that in plain terms?"
+
+If there's a clear financial power imbalance:
+
+- Don't force anyone to disclose. But you can note: "Financial differences affect power whether you name them or not. The question is whether you address it openly."
+
+If they want to decide compensation now:
+
+- "You can start with a provisional model. Try it for a period, then revisit. Consent-based: is this good enough for now, safe enough to try?"
+
+
+### **🏁 After the session**
+
+- Note how the financial conversations went – where was there openness vs. avoidance?
+- Note any power dynamics around financial literacy or financial resources
+- Note any IP ownership disagreements – these need to be resolved before incorporation
+- Bring observations to your PS check-in
+
+
+## :triangular_flag_on_post: **Red flags to watch for**
+
+- One person controlling all financial information or decisions
+- Someone minimizing their own financial needs to match the group
+- "We don't need to talk about money yet" – avoidance that will become a crisis later
+- Financial plans that assume best-case scenarios with no contingency
+- Major gaps in financial literacy that no one is addressing
+- IP ownership assumptions that haven't been discussed – especially if someone brought pre-existing work
+- Compensation discussions where one person's opinion is treated as the default

content/curriculum/PS Guides/7-conflict-resolution-collective-care.md

@@ -0,0 +1,168 @@
+# 7: Conflict Resolution and Collective Care
+
+## Pre-session
+
+- Review Baby Ghosts' [Conflict Resolution Policy](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Policies/Conflict+Resolution+Policy) before session – this is the template participants will adapt for homework
+- Check in with your studio about how their compensation discussions went; any friction that came up is useful for this session
+
+## **What happens in session**
+
+The heaviest session. Studios learn to reframe conflict as data (not failure), distinguish structural from interpersonal conflict, and practice behaviourally-specific feedback. Key tools: the Loving Justice framework (Brave? Kind? Honest? Humble?), the intent/behaviour/impact model ("stay on your side of the net"), and the Window of Transformation (zones of activation). The session covers multi-directional accountability, escalation as care, and the idea that trust comes from repair, not avoidance.
+
+
+:::warning
+**Before this session:** review Baby Ghosts' [Conflict Resolution Policy](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Policies/Conflict+Resolution+Policy). Check in with your studio about how their compensation discussions went – any friction that came up is useful material for this session.
+
+:::
+
+
+### :eyes: **Your role during session**
+
+- Observe how your studio responds to the conflict reframing – relief, resistance, or discomfort can all be informative
+- Watch the activity closely – are they able to use behaviourally-specific feedback or do they slide into judgments?
+- Note whether anyone identifies conflicts they've been avoiding
+- Pay attention to body language during the accountability discussion – who checks out? Who leans in?
+
+
+### 👆 **Your role after session**
+
+- Check in with each studio member (even briefly, via Slack) about how the session landed
+- Make sure they have the link to Baby Ghosts' [Conflict Resolution Policy](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Policies/Conflict+Resolution+Policy)
+- If any studio member seems activated or upset, reach out directly. This session can surface real pain.
+
+
+## **This week's Studio Support Meeting: Conflict Policy and Practice**
+
+### **📚 Materials**
+
+- Baby Ghosts' [Conflict Resolution Policy](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Policies/Conflict+Resolution+Policy) and [Procedures](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Procedures/Conflict+Resolution+Procedures)
+- Loving Justice framework reference
+- Window of Transformation zones reference
+
+
+### :world_map: **Context**
+
+This PS meeting has two parts: (1) helping the studio name an avoided tension, and (2) reviewing the conflict resolution template together. The order matters – naming a real tension first gives the template review practical grounding. But read the room. If the tension-naming conversation goes deep, let it run and abbreviate the template review. The real work is the conversation, not the document.
+
+This may be the most emotionally demanding PS meeting. Be prepared to hold space without trying to fix everything.
+
+
+### **👆 Before the session**
+
+- Review the Baby Ghosts conflict resolution policy and procedures yourself – know the structure well enough to guide a discussion
+- Reflect on what you observed during the session and the compensation discussion last week – is there an unresolved tension you've noticed?
+- Check your own readiness. If you're carrying a lot from your own studio or personal life, be honest with yourself about your capacity to hold space today.
+
+
+### **🌊 Session flow**
+
+#### **Check-in (5 min)**
+
+"How are you feeling after that session? Anything stirred up?"
+
+This isn't a throwaway question. Give it real space. If someone needs to talk, let them.
+
+
+#### **Name one avoided tension (15-20 min)**
+
+:::warning
+***This could be hard.*** Go gently but don't avoid it.
+
+:::
+
+"What conflict or tension has your studio been avoiding? It doesn't have to be big – small avoidances are actually great to examine."
+
+**If no one speaks up immediately**, let the silence sit. Count to 15 in your head before you intervene. Then try:
+
+- "Is there something you've been wanting to bring up but haven't found the right moment?"
+- "Think back to the last few weeks. Was there a moment where something felt off but no one said anything?"
+- "Are there any patterns from the Informal Hierarchy Check-In (Session 4) that you haven't addressed?"
+
+**If something does come up:**
+
+Help them practice the tools from the session:
+
+1. **Behaviourally-specific feedback:** "What did you actually observe? What's the behaviour you can point to?"
+2. **Stay on your side of the net:** "What was the impact on you? Separate that from what you think they intended."
+3. **Loving Justice check:** "Is what you want to say brave? Kind? Honest? Humble?"
+4. **Window of Transformation:** "Where are you right now? Where do you think the other person is? Is this a good time for this conversation?"
+
+**If something big surfaces:**
+
+Don't try to resolve it in this meeting. Help them decide:
+
+- "Is this something you want to keep working through now, or does it need a dedicated conversation?"
+- "Would it help to have a third party present when you continue this?"
+- "What would make it safe enough to keep talking?"
+
+
+#### **Review the conflict resolution template (15-20 min)**
+
+Go through Baby Ghosts' policy together. For each section, ask:
+
+- "Does this make sense for your studio?"
+- "What would you change?"
+- "What's missing?"
+
+**Key areas to discuss:**
+
+**Who initiates:** "In your studio, who would actually be the one to say 'we need to use the process'? Is it comfortable for everyone to do that, or would some people never initiate?"
+
+**Documentation:** "How much documentation feels right? Too little and things get lost. Too much and it becomes punitive."
+
+**Timelines:** "How quickly should you respond to a raised concern? What's realistic?"
+
+**When resolution isn't reached:** "What happens if you go through the whole process and still can't agree? What's the last resort?"
+
+**Escalation:** "Who's your third party? Another studio member? Your PS? Someone outside the program?"
+
+They don't need to finalize a policy today. The goal is to identify what resonates, what needs adapting, and what gaps exist.
+
+
+#### **Close (5 min)**
+
+- "What's one thing you want to commit to about how you handle conflict going forward?"
+- "Is there anything from today's conversation that needs follow-up before next session?"
+- Remind them: Session 8 is the last session. Encourage them to use this week to address anything unresolved.
+
+
+### :star: **Tips**
+
+If no one wants to name a tension:
+
+- Don't force it. "That's okay. The invitation stays open. Sometimes naming something takes longer. You can always come back to this."
+
+If it gets heated:
+
+- "Let's pause. Where is everyone right now?" (Use the Window of Transformation language.) "Is this a conversation we can have right now, or do we need to step back?"
+
+If someone minimizes:
+
+- "You said 'it's not a big deal' – but you brought it up. Can you say more about why it's on your mind?"
+
+If someone deflects to structural issues to avoid interpersonal ones (or vice versa):
+
+- "It can be both. What's the structural part, and what's the interpersonal part? Which one are you more comfortable talking about – and which one are you avoiding?"
+
+If the template review feels abstract:
+
+- "Think about the tension we just discussed. Would this process have helped? Where would it break down?"
+
+
+### **🏁 After the session**
+
+- Note how the tension-naming went – did something real surface, or did the studio stay safe?
+- Note how they responded to the conflict resolution template – did they engage or treat it as a formality?
+- If any individual seems affected, follow up with them directly
+- Bring observations to your PS check-in – especially anything that concerns you about studio dynamics
+
+
+## :triangular_flag_on_post: **Red flags to watch for**
+
+- A studio that insists they have no conflicts – avoidance is not peace
+- Someone who identifies a conflict but then immediately retracts: "never mind, it's fine"
+- Conflict always attributed to one person – scapegoating
+- Political framing used to avoid naming emotional experience (the emotional-political conflation trap from the session)
+- A studio that wants the policy "just in case" but clearly has an active, unnamed conflict
+- Someone who seems shut down or dissociated – check in with them privately after
+- Performative agreement: "I'm fine with whatever the group decides" when they clearly aren't

content/curriculum/PS Guides/8-self-evaluation-pathways.md

@@ -0,0 +1,209 @@
+# 8: Self-Evaluation and Pathways
+
+## **What happens in session**
+
+The final session. Studios do a personal self-assessment (private) and a studio self-assessment (collective, shared with Baby Ghosts). The studio assessment rates seven areas on a 1-5 scale (from "Considering/Reflecting" to "First Draft of Documentation"): values/purpose/alignment, governance, decision-making/meetings, equitable economics, conflict/repair, program reflection, and what's next. The session covers post-program supports (Ghost Guild, workshops, PS recruitment, incorporation resources) and closes with a collaborative zine activity and group celebration.
+
+
+:::info
+This is a closing session. Your role is less about facilitating new content and more about helping your studio reflect honestly and plan for what comes next. The assessments are the core deliverable.
+
+:::
+
+
+### :eyes: **Your role during session**
+
+- Observe how your studio approaches the assessments – honest and reflective, or rushing through?
+- During the studio assessment, note whether they're aligned on their ratings or if there's disagreement about where they actually are
+- Watch for emotional responses during the closing – this program has been intense, and endings can surface unexpected feelings
+- Participate in the zine activity and closing – you're part of this community
+
+
+### 👆 **Your role after session**
+
+- Make sure both assessments get completed (personal assessment individually, studio assessment together)
+- Schedule a final PS meeting for this week to help them complete assessments and talk about next steps
+- Make sure they understand Ghost Guild and post-program supports
+
+
+:::tip
+Your weekly PS sessions end after this week, but you're still part of the community. Many studios appreciate knowing you're available for occasional check-ins as they hit milestones or challenges.
+
+:::
+
+
+## **This week's Studio Support Meeting: Assessments and What's Next**
+
+### **📚 Materials**
+
+- Personal self-assessment form (each member should have their own copy)
+- Studio self-assessment template (on studio Miro board)
+- Community Rule draft from Session 5
+- Any notes or documents the studio has created during the program
+
+
+### :world_map: **Context**
+
+This is your last formal PS meeting with this studio. The goal is to help them complete their assessments with honesty and specificity, and to set them up for continuing this work without you. Resist the urge to sugarcoat or wrap things up neatly. The most useful thing you can do is help them see clearly where they are – strengths and gaps alike.
+
+
+### **👆 Before the session**
+
+- Review your notes from the full program – what patterns have you noticed? What's shifted? What's stayed stuck?
+- Review the studio's Community Rule draft, values map, and any other documents they've produced
+- Prepare your own honest assessment of where the studio is – you'll use this to calibrate if their self-assessment seems off
+- Think about what you want to say to this studio at the close. This matters.
+
+
+### **🌊 Session flow**
+
+#### **Check-in (5 min)**
+
+"How are you feeling about the program ending? What's sitting with you?"
+
+Let this be genuine. Some people will be relieved, some sad, some anxious about what comes next. All of those are valid.
+
+
+#### **Personal self-assessment (10-15 min)**
+
+If they haven't completed the personal assessment yet, give them quiet time to work on it now.
+
+This is private – you don't need to see it or discuss it. But you can offer:
+
+- "Take your time with this. Be honest with yourself."
+- "Where have you grown? Where do you still feel uncertain?"
+- "What do you need from your collaborators that you haven't asked for yet?"
+
+If they've already completed it, ask: "Was anything surprising when you reflected? Anything you want to share?"
+
+
+#### **Studio self-assessment (20-25 min)**
+
+Work through the seven areas together. For each, the studio rates themselves 1-5:
+
+1. **Considering/Reflecting** – Thought about individually, not discussed as a team
+2. **Discussing Collectively** – Talking together but no decisions
+3. **Brainstorming** – Actively generating ideas and exploring options
+4. **Sifting/Sorting** – Narrowing down, making choices, working toward alignment
+5. **First Draft of Documentation** – Something written down – a policy, process, or shared agreement
+
+**Go through each area:**
+
+**1. Values, purpose & alignment**
+
+- "Can each person name your studio's core values? Do those match?"
+- "Do you have a documented values statement or Why/What/How?"
+
+**2. Governance**
+
+- "Where is your Community Rule draft? What's documented vs. still informal?"
+- "Do you have a membership/removal process, even a rough one?"
+
+**3. Decision-making & meetings**
+
+- "Are you using a named framework? Rotating meeting roles?"
+- "What decisions still happen by default?"
+
+**4. Equitable economics**
+
+- "Have you had the money conversations? Compensation, transparency, IP?"
+- "What's decided vs. what's still avoided?"
+
+**5. Conflict & repair**
+
+- "Do you have a conflict process – even informal? Have you used it?"
+- "What tension have you named? What's still unnamed?"
+
+**6. Program reflection**
+
+- "What worked about this program for you? What didn't?"
+- "What do you wish had been different?"
+
+**7. What's next**
+
+- "What's your plan for revisiting governance and values after the program ends?"
+- "Who's responsible for scheduling that?"
+
+**Your role during this:**
+
+If a rating seems inflated – gently push:
+
+- "You rated governance a 4, but last week you hadn't discussed membership or removal. What's your thinking?"
+
+If a rating seems deflated – acknowledge progress:
+
+- "You rated conflict a 2, but you named and addressed a real tension two weeks ago. That's meaningful progress."
+
+If there's disagreement on a rating – that's data:
+
+- "You see yourselves differently on this one. That's worth exploring. What does each of you see?"
+
+Capture the assessment on the Miro board.
+
+
+#### **What's next (10-15 min)**
+
+Help them make concrete plans:
+
+- "When is your next governance review? Put it on the calendar right now."
+- "Who's going to be your accountability partner for keeping up these practices?"
+- "What's the first thing that will slip? How will you catch it?"
+
+Talk about Ghost Guild and post-program supports. Make sure they know what's available.
+
+If anyone is interested in becoming a PS for a future cohort, encourage them to talk to the program team.
+
+
+#### **Close (5-10 min)**
+
+This is your moment. Share what you've observed over the program – what you're proud of, what you're hopeful about, where you think they'll need to stay vigilant.
+
+Be specific. "You've grown" is less useful than "In Session 2, no one would say what they actually needed financially. By Session 6, you had that conversation and it was hard but you did it."
+
+Then let each studio member share something too:
+
+- "What's something you're proud of from the program?"
+- "What conversation did you have that you wouldn't have had otherwise?"
+
+End with care. This matters.
+
+
+### :star: **Tips**
+
+If they rush through the assessment:
+
+- "This is the last structured reflection you'll do with support. Take the time – it's worth it."
+
+If they rate everything high:
+
+- "I'm glad you feel good about your progress. Can I push on a couple of these? I want to make sure the assessment is useful to you going forward."
+
+If they rate everything low:
+
+- "You've done more than you think. Let me reflect back what I've seen over these weeks."
+
+If they're anxious about the program ending:
+
+- "The structures you've built are real. The tools don't disappear. And the Ghost Guild community is there for you."
+
+If emotions come up:
+
+- Let them. This is appropriate. Don't rush past it.
+
+
+### **🏁 After the session**
+
+- Ensure the studio assessment is submitted (goes to Baby Ghosts)
+- Ensure each person has completed or will complete their personal assessment
+- Share your own PS observations with the program team – what this studio needs going forward, what to watch for, where they're strong
+- Thank the studio. Mean it.
+
+
+## :triangular_flag_on_post: **Red flags to watch for**
+
+- A studio that can't complete the assessment because they disagree on where they are – this reveals deeper alignment issues
+- Rushing through to "get it done" – avoidance of reflection
+- Ratings that don't match what you've observed – denial or lack of self-awareness
+- No plan for continuing governance practices after the program – high risk of drift
+- One person taking responsibility for everything post-program – that's not a coop
+- Signs that the program surfaced issues the studio hasn't resolved – make sure the program team knows

content/curriculum/PS Guides/pre-program-onboarding-and-prep.md

@@ -0,0 +1,48 @@
+# Pre-program: Onboarding and Prep
+
+# **Your first Studio Support Meetings**
+
+
+:::info
+Use this list to get a baseline read on your studio. These are things to *notice and gently explore* over your first couple of conversations. No need to interrogate, and you don't need to go through all of them.
+
+:::
+
+
+### **Relational foundation**
+
+- How long have they known each other? Have they made anything together before?
+- How do they currently make decisions? (Note who answers this question.)
+- What happens when they disagree?
+- Has anyone left a previous collaboration? What happened?
+- Who's doing most of the talking right now? Who's quiet?
+- Is there evidence of trust (or trust-building potential) in the group?
+
+
+### **Capacity and commitment**
+
+- Is everyone working on this full-time, part-time, or around day jobs?
+- Are time contributions roughly equal? If not, how are they thinking about that?
+- What happens if someone needs to step back or leave?
+- Who has business/admin skills? Financial literacy? Project management?
+- Is there openness about strengths *and* limitations?
+
+
+### **Game related**
+
+- Where is the project at? (Concept, prototype, production, shipped?)
+- Who holds the creative vision? Is that shared or concentrated?
+- Have they discussed IP ownership yet?
+- What are the core disciplines in the group? (art, code, design, audio, writing, production?)
+- What's missing? Are they aware of the gaps?
+- Has anyone worked in games professionally before? In what capacity?
+
+
+#### **What you're doing with this information:**
+
+- Building your own picture of the studio's dynamics, strengths, and risk areas.
+- You don't need to resolve anything yet, just notice.
+- Bring observations to your PS check-in.
+
+
+*Credit:* **Effective Practices in Starting Co-ops** *and Christine Clarke of __[Freedom Dreams](https://www.freedomdreamscoop.com/)__ for inspiration/starting points.*

content/curriculum/Sessions/Session 0 – Kickoff + Onboarding.md

@@ -0,0 +1,191 @@
+# Session 0: Kickoff + Onboarding
+
+*Peer Supports: See **PS Guide: Session 0** for pre-session tasks.*
+
+---
+
+## Welcome
+
+- Tag Yourself activity
+
+---
+
+## Intro - 2 min
+
+Session 0 orients us to the shared work ahead. This opening session grounds participants in the purpose and structure of the program while setting the tone for a peer-driven, care-centred space.
+
+We'll begin building the relational trust and shared accountability that will carry us through the following 8 sessions. We'll reflect on our own privileges and lived experiences. By the end of this session, we'll have a shared understanding of how we'll learn together. This is the beginning of practicing cooperation together.
+
+"The most important thing is if there's **trust** between the people in the group because that's what carries it through." - Russ Christianson
+
+---
+
+## Agenda
+
+### Welcome, land acknowledgement, values - 10 min
+
+- Quick round: name, pronouns, location, why you're here  
+- Acknowledge land and virtual space, and share our values  
+    - We acknowledge and thank all those who have struggled for workers’ rights and racial, economic, and environmental rights and emancipation  
+- We are recording this session for team members who can't attend  
+- Please post questions as we go in the chat  
+- Opportunity to ask more questions during Q&A at end  
+- If you have any access needs, put it in the chat or DM @jennie or @eileen
+
+### Participant intros - 15 min (3 mins each)
+
+1. Each team says hello - have one person talk for the team and the others chime in the chat with:  
+    - name, pronouns, location  
+2. Tell us about your game - *briefly*  
+    - can share pictures in the chat if you want  
+3. Biggest studio pain point *right now*
+
+### Peer Support team intros - 5 min
+
+- Who is paired with who  
+- What Peer Support sessions look like
+
+---
+
+### Where you are: The co-op development journey - 10 min
+
+**SLIDE: Coop Journey Map** *(visual showing: pre-formation to formation to operation)*
+
+First, let's look at the statistics:
+
+- Small business startup success rate: ~20% (8 in 10 fail)
+- Cooperative startup success rate: ~40% (6 in 10 fail)
+- Co-ops significantly outperform conventional startups – but it's still not a guarantee
+
+**You're still going against the odds. But it's a worthwhile thing to do, because you learn so much.**
+
+Being a co-op improves your odds, it doesn't eliminate risk.
+
+This program focuses on **pre-formation** - the relational and governance groundwork that determines whether your co-op will thrive or struggle. 
+
+Most resources out there focus on the legal and operational stuff: how to incorporate, how to file paperwork, how to structure bylaws. That matters, of course! But it's not where studios fail.
+
+Studios fail because of unspoken assumptions about money, time, and commitment; wishy-washy and undocumented governance; conflict avoidance; unexamined power dynamics
+
+This program exists to build the foundation *before* you incorporate. By the end of this program, you'll have shared values that you know how to put into action. We'll walk you through designing and practicing cooperative governance structures. You'll know how to decide *how to decide*! and we'll test low-stakes decisions. And you'll have drafted conflict tools ready for when (NOT IF!) tensions arise.
+
+**You are here:** Pre-formation and building your relational infrastructure
+
+**What comes after:** Incorporation support, ongoing community (Ghost Guild), and continued learning. We'll talk about pathways in Session 8.
+
+---
+
+### Program overview - 10 min
+
+- Program schedule, session themes, and format
+- Gamma Space / Slack explanation
+- Slack structure: main channel(s), cohort channels, project channels, random and other general channels
+- Expectations for engagement (Slack reflections, homework, participation)
+- How to participate
+- How to book with us
+- Review accessibility practices (captions, breakout choices, asynchronous options)
+- Tools we'll use (Miro, Slack Canvas, Huddles)
+
+*Note: Much of this info will also live in a Slack Canvas for reference.*
+
+This program will give you tools to notice when informal hierarchy forms, have hard conversations about money, power, and expectations, make decisions collectively, and navigate conflict as valuable data. It will NOT make you hierarchy-free, tell you exactly how to structure your co-op, eliminate disagreement, or do the hard conversations for you. *We're here to support you, but the work is yours.*
+
+---
+
+### Friction is part of the work - 5 min
+
+Before we build our community agreements, we want to chat about something that has come up in every previous cohort.
+
+This program will ask you to have hard conversations - about money, about power, about what you actually want from this collaboration. Some of those conversations will be *uncomfortable*. You might discover that your group is less aligned on values than you assumed. You might have disagreements you've never had before. Someone might go radio silent, and someone might get defensive.
+
+Examples:
+
+- "I've been doing most of the work and I'm starting to resent it."  
+- "We said we'd share decisions equally, but one person always gets the final word."  
+- "I thought we agreed on this, but I actually don't think I had a real say."  
+- "I can only commit 10 hours a week and you're working 40 - how do we make that fair?"  
+- “I want to leave the studio.”
+
+This is normal. This is the work!
+
+We bring these questions up to normalize friction. And because unspoken assumptions are where studios fall apart. The friction you feel now, when the stakes are low and you have support, is infinitely better than discovering it later when you're under deadline pressure or financial strain.
+
+A few things to reframe…
+
+- Discomfort often means something important is coming up.  
+- Disagreement tells you something isn't clear and gives you an opportunity to include more people.
+- If everything feels easy, you might not be going deep enough.
+
+We're here to support you through the hard parts - that's what Peer Supports are for. But we can't do the hard conversations for you.
+
+---
+
+### Commitment and permission - 5 min
+
+Let's talk about what commitment actually means in this program.
+
+Time - About 2-3 hours per week (sessions + homework + Studio Support meetings). Some weeks will be heavier. If you can't make a session, let us know - recordings are available, but live participation is really important.
+
+Openness - This work asks you to be vulnerable with your collaborators: To say what you actually think, to hear things you might not want to hear - this will take energy and might be unfamiliar. Give it your best shot.
+
+Money - You're receiving a grant as part of this program. That comes with accountability - to yourself, your studio, and the cohort.
+
+Purpose - Why does your studio need to be a co-op? Not "why are co-ops good" but what specific problem does working cooperatively solve for you that you couldn't solve another way? 
+
+You have permission to leave early - If you realize partway through that this isn't the right time, or this isn't the right team, or you need to step back - that's okay. It's better to face that than to go through the motions. We'd rather you make an honest choice for yourself.
+
+Leaving isn't failure. *Sometimes it's the most cooperative thing you can do.*
+
+---
+
+### Code of conduct & community agreements - 15 min
+
+Now let's build some shared agreements for how we'll be together.
+
+We'll start with a few agreements and build from there. We are naming what we *need* to do the hard work together.
+
+**Activity:** Collective drafting via Miro
+
+- We'll start with a few prompts  
+- Add your own via stickies  
+- Emoji reactions  
+- We won't finalize today - we'll revisit and refine
+
+**Starter prompts:**
+
+- What do you need to feel safe raising a concern?  
+- What helps you stay present when things get uncomfortable?  
+- How do you want to be supported when you're struggling?  
+- What makes you feel able to jump into a conversation?
+
+---
+
+### Activity: Power Flower overview - 10 min
+
+Your first piece of individual work is a reflection on your own power and privilege.
+
+**Power Flower** - a tool for mapping the identities and experiences you bring into this space.
+
+This is private and for your own reflection. Baby Ghosts won't see it. Your studio won't see it unless you choose to share. We'll use it as a jumping-off point in Session 1.
+
+- What lived experiences or identities shape how you enter this space?  
+- What kinds of influence or resources (social, economic, relational) do you carry?  
+- Where do you need support?  
+- What hopes or expectations are you bringing into this program?
+
+Complete this in your private Miro board before Session 1.
+
+---
+
+### Closing - 5 min
+
+- Each person shares one intention or hope for the program  
+- Reminders: next session prep, Slack channels to check, Power Flower homework
+
+---
+
+## Homework
+
+1. **Complete your Power Flower** – Use the template in your private Miro board. Reflect on the identities, experiences, and forms of power you bring into this space. This is just for you – we'll use it as a jumping-off point in Session 1.
+
+---

content/curriculum/Sessions/Session 1 – Coop Principles and Power.md

@@ -0,0 +1,271 @@
+# Session 1: Coop Principles and Power
+
+## Welcome
+
+- Slide: Tag Yourself activity
+- Slide: Anonymous feedback form reminder
+
+---
+## Intro - 3 min
+
+Working in an environment that focuses solely on shipping, profit, and growth denies us the opportunity to practice our values collectively. Worse, the outcome of those capitalist values is exploitation and dehumanization of everyone but whoever is at the top of the org chart. How can we connect with our deepest-held values to shape collective practices that challenge this harmful hierarchy?
+
+We have some guidance to start with: The principles adopted in 1995 by the International Cooperative Alliance (ICA), which now form the ethical foundation for cooperative work around the world and are deeply reflected in cooperative history and practice in the Global South. We'll trace a line from these principles to your personal and shared values, and then to what cooperative practice can look like in your context.
+
+Through this work, we can create a culture that stands up to extraction and burnout, and practice something different in its place.
+
+---
+
+## Agenda 
+
+Today we’ll be talking about:
+
+- How to cooperate (cooperative capacities)  
+- Coop histories/lineages  
+- The ICA cooperative principles  
+- How to move from the principles to values
+
+### Check-in - 5 min
+
+*Thinking back on the Power Flower reflection you did...*
+
+- what's one thing you noticed about yourself that you hadn't named before?  
+- no need to share details, unless you are compelled! Just notice what came up
+
+---
+
+### Cooperation is a skill, not a trait - 5 min
+
+We've been socially and economically shaped by systems that reward competition, individual achievement, and hierarchy. Most of us were just never taught *how* to cooperate.
+
+"Most human beings have a natural propensity to cooperate." -- Russ Christianson, *Effective Practices in Starting Co-ops*
+
+The capacity exists. We already practice solidarity economics in daily life without calling it that when we contribute to a GoFundMe or babysit our neighbour's kids. But these practices get buried under what Black economist Jessica Gordon Nembhard calls "the assumptions of neo-liberal capitalist ideology."
+
+Can cooperation be recovered and practiced until it's reliable?
+
+That's what this program is for. We're not here to convince you cooperation is good. Pretty sure you already know that. We're here to build the muscle and to practice until cooperative decision-making becomes your default.
+
+---
+
+### The skills of cooperation - 7 min
+
+So what does "cooperation is a skill" actually mean? *What* are the skills?
+
+We're going to introduce tools throughout this program, but tools only work if you have the *underlying capacities* to use them. A consensus process doesn't help if no one can sit with discomfort long enough to hear a dissenting view.
+
+Here's what we'll be practicing:
+
+**Active listening**  
+This means unlearning the tendency to simply wait for your turn to talk. It means actually focusing on the other person and trying to understand what they really mean, especially when you disagree. One practice to support this is reflecting back what you hear. You can also take notes.
+
+**Honest communication**  
+Without making accusations, say what you actually think, and use "I" statements. The purpose is to open conversation up wider.
+
+**Perspective-taking**  
+Your collaborators experience situations differently from you, and from each other. Try to put yourself in their position/mindset and hear what they are telling you about what they are feeling.
+
+**Emotional self-regulation**  
+It can be difficult, without prior practice, to stay present when things get uncomfortable instead of shutting down, lashing out, or agreeing just to make the tension stop. Notice discomfort and choose how to respond rather than just reacting.
+
+**Self-awareness about your patterns in groups**  
+Do you talk first? Go quiet when you disagree? Say yes to avoid tension? Take over tasks because it's faster than explaining? Notice your ingrained habits!
+
+**Giving and receiving feedback**
+This is a tough one for a lot of people. When you have a concern, do you hedge so much it disappears? And when you hear critical feedback, do you get defensive or collapse? Both directions are skills. Look at feedback as a *gift*.
+
+None of these are natural talents, but all of them can be practiced. In fact, you'll be practicing them throughout this program, starting next session!
+
+*Sources: Munro, "United we stand: fostering cohesion in activist groups," Interface 13(1), 2021*
+
+---
+
+### Cooperative lineages – and whose knowledge gets credited - 10 min
+
+The foundational principles of cooperatives are rooted in survival. But the Rochdale Pioneers of 1844, often credited as cooperative "founders," didn't invent cooperation – they simply codified practices that had existed for millennia. We’ll cover those principles in a minute, but first let’s talk about the longer lineages of cooperative history.
+
+- Indigenous communities worldwide practiced mutual aid, collective resource management, and consensus decision-making long before European contact. Many Indigenous governance systems also held space for Two-Spirit people in leadership and decision-making roles.  
+- Enslaved and formerly enslaved Black communities in the Americas created mutual aid societies, burial societies, and informal credit systems out of necessity and survival  
+- Women formed cooperative childcare networks, domestic worker collectives, and community support systems -- often invisible and uncredited  
+- Immigrant communities built cooperative stores, housing, and financial institutions when mainstream systems excluded them  
+- Queer and trans communities built mutual aid networks, collective housing, and care systems - often out of crisis. Marsha P. Johnson and Sylvia Rivera's STAR (Street Transvestite Action Revolutionaries) in 1970s New York provided communal shelter, food, and support for homeless trans youth of colour, organized entirely on principles of shared responsibility and collective care  
+- During the AIDS crisis, queer communities created cooperative care networks, buyers' clubs to share medication, and mutual aid funds when governments and institutions abandoned them
+
+*The Combahee River Collective - Black lesbian feminists organizing in the 1970s - articulated what we now call intersectionality. Cooperative movements have always been strongest when they refuse to separate one axis of liberation from another*
+
+[TODO-IMAGE-01: Cooperative history image. By Roseleechs – Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=119409579]
+
+The Rochdale Pioneers formalized these practices into a movement. But when we credit them as "founders," we invisibilize the communities who developed and sustained cooperative practices for generations under conditions of oppression.
+
+Source: *Locating the Contributions of the African Diaspora in the Canadian Co-operative Sector* [WIKILINK-01: needs URL] Additional info: [Indigenous Governance and Tomorrow's Democracy](https://www.colorado.edu/lab/medlab/2025/07/28/indigenous-governance-and-tomorrows-democracy-join-conversation)
+
+This matters for us because you may already hold cooperative knowledge. It could be in your family, your culture, your community.
+
+Consider your own "cooperative lineage":
+
+- Did you grow up with childcare swaps, community gardens, or potlucks?  
+- How did your family handle resources when money was tight? Who did they turn to?  
+- What decision-making traditions come from your culture?  
+- Have you been part of a band or community organization that shared resources or made decisions collectively?
+
+Or:
+
+- Why did you become interested in forming a cooperative?
+
+Most of these practices go unnamed as "cooperative" but they are part of a long, global, grassroots, and informal tradition.
+
+There are many types of cooperatives (coop housing, community land trusts, community financing like credit unions, worker cooperatives like you’re trying to build) – but also barter clubs, fair trade, solidarity markets.   
+[TODO-IMAGE-02: Types of cooperatives/solidarity economy image from art.coop]
+
+Cooperatives are expansive and we can add skills to your toolkit!
+
+Share one cooperative practice from your experience in the chat. *And pay attention to what values are present.*
+
+### Small groups -- mixed studios (3-4 people) - 15 min
+
+- Share your cooperative lineage story  
+- What values were present in that experience?  
+- Each group identifies 3-5 values they heard across their stories  
+- What need brought your studio together? What were you each missing that cooperation addresses?
+
+Brief large group share - 5 min: Each group shares 1-2 values they identified.
+
+---
+
+## The 7 Cooperative Principles - 10 min
+
+The values you just named have been recognized and formalized by cooperative movements worldwide. In 1995, the International Cooperative Alliance adopted these 7 principles that now guide cooperative work globally.
+
+*For each principle, consider: How might your co-op incorporate this principle? What policies or practices would bring it to life?*
+
+### 1. Voluntary and Open Membership
+
+Cooperatives are voluntary organizations, open to anyone able to use their services and willing to accept the responsibilities of membership, without gender, social, racial, political or religious discrimination.
+
+### 2. Democratic Member Control
+
+Cooperatives are democratic organizations controlled by their members, who actively participate in setting their policies and making decisions. Your board of directors is accountable to the membership. Each member has one vote.
+
+- *How will the co-op balance this with the reasonable interests of different classes of members?*
+
+### 3. Member Economic Participation
+
+Members contribute equitably to, and democratically control, the capital of their cooperative.
+
+- *Consider the share values, annual fees, fees-for-services, and other financial commitments that members will have to meet.*
+
+### 4. Autonomy and Independence
+
+Cooperatives are autonomous, self-help organizations controlled by their members. If they enter into agreements with other organizations, including governments, or raise capital from external sources, they do so on terms that ensure democratic control by their members and maintain their cooperative autonomy.
+
+- *What policies are needed around contracts, hiring contractors, accepting donations, or taking investment?*
+
+### 5. Education, Training, and Information
+
+Cooperatives provide education and training for their members, elected representatives, managers, and employees so they can contribute effectively to the development of their cooperatives.
+
+- *What education is needed about the rights and responsibilities of membership? About other topics related to your coop's activities?*
+
+### 6. Cooperation Among Cooperatives
+
+Cooperatives serve their members most effectively and strengthen the cooperative movement by working together through local, national, regional, and international structures.
+
+### 7. Concern for Community
+
+Cooperatives work for the sustainable development of their communities through policies approved by their members.
+
+Summary source: *A People-Centred Path for a Second Cooperative Decade* [WIKILINK-02: needs URL] - ICA 2020
+
+Nobody carved the 7 Principles into stone tablets and carried them down the mountain. The ICA has revised the principles three times - in 1937, 1966, and 1995 - because cooperative practice changes. You don't have to follow the rules perfectly to be a coop. But hold on to the core: democratic control, shared ownership, and surplus flowing to workers based on their labour. Everything else can be adapted to your studio's capacity and interests.
+
+### The values beneath the principles
+
+The principles give us structure. The values give us *why*. The International Cooperative Alliance summarizes it this way:
+
+*"Cooperatives are based on the values of self-help, self-responsibility, democracy, equality, equity and solidarity. In the tradition of their founders, cooperative members believe in the ethical values of honesty, openness, social responsibility and caring for others."*
+
+These are commitments to how we treat each other.
+
+---
+
+## From principles to your values - 3 min
+
+What values guide *your* work or collective efforts?
+
+Values are *beliefs* that motivate us to*act* one way or another. They guide our behaviour.
+
+We each adopt values from a combination of our upbringing, the communities we are part of, the dominant culture, and other influences in our lives. Just like an individual's values guide how that person acts, organizational values guide how the *group* acts and makes decisions collectively.
+
+Values also define scope and ethical constraints.
+
+[Sociocracy 3.0: Agree on Values](https://patterns.sociocracy30.org/agree-on-values.html)
+
+---
+
+### How do we collaborate when we mean different things? - 2 min
+
+Words are vague, communication is fraught, and we're all coming in from different backgrounds. The best thing we can do to support the cooperative principles of collaboration is to try and find common ground.
+
+Where do we meet each other? And how do we build from there?
+
+---
+
+## Homework - 10 min
+
+1. **Journal about your values** – What values guide your work or collective efforts? Your values can be discovered through observation. Your task isn't to decide what matters to you, but to notice what already does.
+    - What holds your attention without effort?
+    - What do you find yourself doing when no one is watching?
+    - What topics consistently generate strong emotional responses?
+    - When have you felt most alive or fulfilled?
+
+1. **Do the team values map with your Peer Supports** – Use your PS session to do the values mapping exercise as a team. Where do you align? Where do you differ?
+
+2. **Prep individually for "The Talk" (Session 2)** – Next session, you'll practice having direct conversations about money, time, skills, and decision-making with your collaborators. Reflect on these questions – **write your answers down** before we meet. Try to time-box to about 5 minutes per section.
+
+   **Financial reality:**
+
+    - How much do you need to make monthly to participate in this studio?
+    - What's your current financial capacity to contribute?
+    - How important is immediate income vs. long-term equity?
+
+   **Time and availability:**
+
+    - What's your actual time availability per week?
+    - What are your non-negotiable boundaries?
+    - How do you handle competing priorities?
+
+   **Skills and contributions:**
+
+    - What do you excel at vs. what drains you?
+    - Where do you want to grow vs. where you're already expert?
+    - How do you prefer to contribute when you're overwhelmed?
+
+   **Decision-making styles:**
+
+    - How do you prefer to make decisions under pressure?
+    - When do you need more information vs. when do you trust your gut?
+    - How do you handle disagreement?
+
+   And finally: **Does being part of this studio make you feel something? What is that feeling?**
+
+   Adapted from Obvious Agency's "The Talk" worksheet.
+   
+   *These are for **you** first. You'll share with your team in Session 2.*
+
+---
+
+## Closing - 5 min
+
+We've identified values that guide us individually and found connections to cooperative principles. But now comes the hard part: How do we actually *practice* these values together?
+
+It might seem easy and fun to chat about these ideas with your collaborators, but until you are in conflict, or under financial or deadline pressure, you don't really know how everyone will hold on to those values.
+
+Studios built around a shared problem - "we can't afford to make games alone," "we refuse to work in exploitative conditions again" - tend to hold together under that pressure. Studios built around a shared *aesthetic* preference for cooperation sometimes don't. Try to notice which one is yours.
+
+The industry tells us to brute force our way through these situations – with the boss ultimately "resolving" the issue the way they want, probably guided by "move fast and figure it out later." But cooperative work requires something different. What Indigenous organizer Ruth Łchav'aya K'isen Miller calls "patience for the pace of trust."
+
+Next session, we'll explore what it actually takes to align with collaborators beyond just sharing values on a Miro board. Even the closest friends can discover they have very different expectations about work, money, and decision-making when those conversations inevitably come up.
+
+Use your Peer Support session this week to start talking about your values as a team.
+
+---

content/curriculum/Sessions/Session 2 – Shared Purpose and Alignment.md

@@ -0,0 +1,192 @@
+# Session 2: Shared Purpose and Alignment
+
+## Welcome - 5 min
+
+- Slide: Tag Yourself  
+- Slide review: What we've learned so far  
+    - we've learned the history of cooperatives, the principles, and how we each know these practices from our own lineages  
+    - we've identified our personal values and started mapping them as teams
+
+---
+
+## Intro - 10 min
+
+"Patience for the pace of trust."
+
+- Ruth Łchav'aya K'isen Miller (Dena'ina Athabaskan, Curyung Tribe), co-founder of Smokehouse Collective
+
+*Ruth Łchav'aya K'isen Miller, "[An Alaska Native mutual aid network tackles the climate crisis](https://www.hcn.org/issues/56-1/food-an-alaska-native-mutual-aid-network-tackles-the-climate-crisis/)," High Country News, 2024.*
+
+*via Burton, Antoinette. [“Moving at the Speed of Trust”? Course Correction Needed](https://visiblemagazine.com/moving-at-the-speed-of-trust-course-correction-needed/)*  
+*VISIBLE Magazine, 5 Dec. 2024* 
+
+There is no set pace or speed at which this work should happen. Resisting external time pressures can cost opportunities or just make you feel an anxious sense of FOMO. But taking the time to move in concert with your collaborators, building shared understanding and purpose, will set the foundation for work that lasts and relationships that can hold complexity.
+
+The industry normalizes crunch, exploitation, and toxic competition as "just how games are made." These practices are in perfect opposition to those that ensure the stability and long-term sustainability of a studio. They are also the main failure point of the industry, destroying amazing teams and causing a ripple effect of harm.
+
+Many indies assume that because they are friends (or share political values) that they'll naturally work well together. But being pals and being aligned politically does not mean you share **work** values, **decision-making** styles, or **financial** expectations. Without putting intentional time and effort into alignment, even the closest relationships can crumble when those difficult conversations inevitably come up.
+
+In a cooperative, instead of a boss solving problems through their authority, democracy becomes everyone's responsibility. Liberating? Terrifying? Yes. Why? Because *most of us were never taught the skills required to work collectively.*
+
+This session will focus on moving slowly and with intention to create the conditions where disagreement can arise *without destruction*. We will look at some practical skills to guide conversations you might have with your actual collaborators.
+
+---
+
+## Agenda
+
+### Check-in - 10 min
+
+Two prompts:
+
+1. *from your team's values mapping: what's one thing you learned about where your team aligns or diverges*  
+2. *what's one assumption you've made about working with others that turned out to be wrong?*
+
+Share in the chat or unmute if you’re comfortable.
+
+---
+
+### The alignment challenge - 15 min
+
+We often assume we know the main goals for our projects, or think we have common language to describe scale and pace. We don't realize we may not be equally committed, or that we have different boundaries.
+
+A big red flag is this attitude: "We're all friends, we never fight, we'll just figure it out as we go." More than friendship is required to set a foundation of true trust and solidarity in a cooperative. We have seen more studios fail due to interpersonal/values conflicts than lack of funding or creative/technical issues.
+
+Once you start to do this work, you may realize you are not as aligned as you thought you were, and that's okay! However, try to examine why there is disagreement or how organizational power may be playing a role.
+
+- In traditional studios, **the boss decides** when there's disagreement.  
+- In cooperatives, unresolved misalignment can become **paralysis**.
+
+#### Common pitfalls
+
+- "We all just want to make good games" - don't we all! Too vague.  
+- assuming shared politics = shared work values (activism != cooperative governance)  
+- rushing past uncomfortable conversations like money and centralized power  
+- defaulting to traditional studio roles
+
+#### Creating safety for hard conversations
+
+- not everyone needs identical commitment levels - **you can all be different!!**  
+- better to get conflicts out in the open early than let them fester, even if it feels scary  
+- focus on systems
+
+#### Alignment != agreement
+
+**Alignment** - Shared understanding of direction, *even with different motivations*
+
+**False consensus** - Agreeing to avoid conflict (recipe for resentment)
+
+**Healthy disagreement** - Different perspectives within shared values framework
+
+Today we'll practice three core conversations…
+
+---
+
+## Activity: "The Talk" - 35 min
+
+*Adapted from "The Talk: A Tool for Putting Values and Real Lives at the Forefront of Work" by Deen Rawlins (Obvious Agency), with modifications by Daniel Park*
+
+In your studio channels, with your Peer Support, practice these conversations.
+
+### Facilitation setup
+
+You've each thought about these questions individually (Session 1 homework). Now you're sharing with your team. The goal isn't to solve everything today - it's to get the conversation started. You'll keep picking up these threads in your Peer Support sessions.
+
+- When someone is speaking, listen. Hold responses until discussion time.  
+- There are no wrong answers  
+- Don't try to avoid discomfort. That's the good stuff.
+
+Format for each round:
+
+- Each person answers in turn (1.5-2 min each)  
+- Use the Miro timer  
+- After everyone answers, brief open discussion  
+- Then move to next round
+
+You won't come to a conclusion today. You'll have a chance to talk about these topics with us and your Peer Supports throughout the program.
+
+---
+
+### Round 1: Financial reality - 8 min
+
+- How much do you need to make monthly to participate?  
+- What's your current financial capacity to contribute?  
+- How important is immediate income vs. long-term equity?
+
+[FACIL-01: See facilitator guide for observation notes]
+
+---
+
+### Round 2: Time & availability - 8 min
+
+- What's your actual time availability?  
+- What are your non-negotiable boundaries?  
+- How do you handle competing priorities?
+
+[FACIL-02: See facilitator guide for observation notes]
+
+---
+
+### Round 3: Skills & contributions - 8 min
+
+- what do you excel at vs. what drains you?  
+- where do you want to grow vs. where you're already expert?  
+- how do you prefer to contribute when you're overwhelmed?
+
+[FACIL-03: See facilitator guide for observation notes]
+
+---
+
+### Round 4: Decision-making styles - 6 min
+
+- How do you prefer to make decisions under pressure?  
+- When do you need more information vs. when do you trust your gut?  
+- How do you handle disagreement?
+
+[FACIL-04: See facilitator guide for observation notes]
+
+---
+
+### Debrief - 5 min
+
+[FACIL-05: See facilitator guide]
+
+What surprised you? Where did you notice alignment? Where did you notice difference/divergence?
+
+You probably noticed that a lot came up – and that's okay! We're going to keep talking about each of these areas as we go. All we did today is get the convo going. There's lots more work to do.
+
+Remember: success for your studio is defined by your needs and values, not the industry's.
+
+---
+
+## Closing - 5 min
+
+Reflect (can share or just think):
+
+- what are some of the tension points that came up during The Talk?  
+- what's one conversation you now realize you need to have with your collaborators?  
+- how might you redefine success to fit the needs of your studio?
+
+Next session, we'll take the values you've identified and turn principles into practices you can actually use when decisions get hard.
+
+---
+
+## Homework
+
+1. **Continue "The Talk" in your PS session** – Go deeper on whichever round brought up the most tension or uncertainty.
+
+2. **Reflect individually on tension points** – Write down:
+    - something that surprised you about a teammate's answer
+    - one place where you felt tension but didn't say anything
+    - a question you wish you'd asked but didn't
+
+   Bring these to your PS session. You don't have to share them with your full team yet.
+
+3. **Think through scale and pace individually** – Before your next PS session, take some time to think through where you see your studio in 1/3/5 years. How many people on the team? One game? Multiple? What platforms? What are your goals – sustainability? Growth? Other measures of success?
+
+   Then ground it in reality: who are your players? (Do you know?) What's your revenue model? (Game sales? Services? Grants? Mix?) Can this sustain you? For how long?
+
+   We're not here to kill dreams. Just like any business, a cooperative needs a viable revenue plan. A studio that is not economically viable isn't sustainable, no matter how good the values are. Because if you don't have that, you don't have anything else.
+
+   Bring your notes to your PS session. You'll use these as a starting point for ongoing conversations about shared language and alignment around scale, pace, and what success looks like for your studio.
+
+---

content/curriculum/Sessions/Session 3 – Actionable Values and Impact.md

@@ -0,0 +1,196 @@
+# Session 3: Actionable Values and Impact
+
+*Peer Supports: See **PS Guide: Session 3** for pre-session tasks.*
+
+---
+
+## Welcome
+
+- Slide: Tag Yourself activity
+
+---
+
+## Intro - 3 min
+
+Over the last two sessions, we've covered **WHY** cooperatives matter to game developers who are challenging toxic industry norms, **WHAT** we want to build through shared purpose and values, and now we will dive into the **HOW**: The day-to-day tools you need to make democratic work... work! These tools are *technologies for liberation*, and every small step we take toward collectivism matters.
+
+You've identified your values (Session 1) and started aligning with your collaborators (Session 2). But values on paper (or in your Miro board) don't prevent burnout or resolve conflict. This session introduces two tools to make values operational. Something you can return to when decisions get hard.
+
+With these tools, we can change our work relationships immediately by choosing:
+
+- consent over coercion  
+- transparency over secrecy and gatekeeping  
+- collective care over competition  
+- slow over fast  
+- horizontal over hierarchical
+
+### Check-in - 5 min
+
+Last session you practiced The Talk and worked on scale and pace definitions with your team.
+
+*what's a tension that came up - something that surprised you, or that you're still thinking about?*
+
+---
+
+### Case study from PS Presenter - 10 min
+
+
+---
+
+### Scenarios - 15 min
+
+So let's practice. We'll give you two scenarios. *Start with your values before you jump to the solution.*
+
+**Scenario 1:** Someone is really excited about your studio and really wants to join, but you don't have funding to pay them. They claim that they just want experience. How do you handle this?
+
+**Scenario 2:** A high-profile client who is legit and proven to have the funding wants to commission you to make art for them using generative AI. Your studio is at an early stage where getting clients at all is challenging. What do you do?
+
+*Take 3–4 minutes to discuss each scenario. Remind them: Start with your values before you jump to the solution. What values came up? How did they shape the conversation?*
+
+---
+
+## Tying your values to practices - 5 min
+
+You've identified values. You've had hard conversations about alignment. But how do values actually show up day-to-day?
+
+Values that live only in a document or a Miro board don't prevent burnout, resolve conflict, or guide decisions under pressure. The gap between "we value transparency" and *actually practicing* transparency is where most studios struggle.
+
+They also don't hold your studio together when someone asks "why are we even doing this?" In a Ghost Guild session after the program, we will work on public narrative - the practice of telling the story of why your studio exists in a way that actually moves people. For now, just notice: When you're working through Why/What/How, your "Why" is the beginning of that story. Hold tight to it!
+
+This section introduces two tools to close that gap:
+
+1. **Why/What/How framework** - for turning values into concrete practices. You’ll work on this with your Peer Supports.  
+2. **Layers of Effect** - for checking whether potential outcomes from your actions match your intentions
+
+Both tools give you something to return to when decisions get hard, when you're under deadline pressure, or when you realize you've drifted from what you said mattered.
+
+---
+
+## Tools and frameworks
+
+*for practicing values and assessing impact*
+
+### Why/What/How framework - 10 min
+
+#### Using the framework
+
+**First, identify the problem, decision, activity to analyse.**
+
+The *order matters*: Why, then What, then How. And your values should guide all three levels.
+
+**WHY** - Why does this value matter to us? What's at stake? Example: "We value transparency because secrecy entrenches power and excludes people from decisions that affect them."
+
+**WHAT** - What does practicing this value look like? What are we committing to? Example: "All financial information is accessible to all members. Compensation is open."
+
+**HOW** - How will we actually do this? What specific activities or outputs? Example: "Monthly financial summaries shared in Slack. Quarterly budget review meetings. New members oriented to finances in onboarding."
+
+You’ll work on this one more with your Peer Supports!
+
+---
+
+### Layers of Effect - 25 min
+
+The second tool helps you see impact before (and after) you act.
+
+**Layers of Effect** is a framework for mapping the ripple effects of your decisions - both intended and unintended. It's adapted from an exercise by UX designer Kat Zhou.
+
+[Miro template](https://miro.com/templates/layers-effect-template/) [FACIL-08: add to studio boards]
+
+#### How it works
+
+The framework uses three concentric rings:
+
+**Primary Effects** (centre ring) These are the *fundamental intentions* behind your activity - the direct, immediate impacts you're trying to create. For instance, a cooperative might focus on equitable profit sharing among all members, or prioritize sustainable and fair labour practices.
+
+*Questions to ask:*
+
+- What direct benefits will people experience?  
+- Who might be immediately excluded or harmed?  
+- What vulnerabilities are we creating?  
+- What breaks immediately?
+
+**Secondary Effects** (middle ring) These are *known but perhaps not immediately obvious* impacts. An example could be the cooperative's influence on promoting diversity and inclusion in the games industry, or its role in advocating for mental health awareness through its games and community interactions.
+
+*Questions to ask:*
+
+- How could positive behaviours spread through networks?  
+- What dependencies or new risks are we introducing?  
+- Who bears the burden of adaptation?  
+- What erodes over months?
+
+**Tertiary Effects** (outer ring) These involve *unforeseen consequences* that arise from your activities. This might include setting new industry standards for ethical game development, or inadvertently creating a platform for global collaboration and cultural exchange among developers and players.
+
+*Questions to ask:*
+
+- What industry standards could this establish?  
+- What long-term societal impacts might emerge?  
+- Which communities or ecosystems pay the price?  
+- What shifts over years?
+
+#### At each layer, think about:
+
+- Who gains?  
+- Who pays?  
+- Who's invisible but affected?
+
+*As effects move outward, who becomes responsible for unintended consequences?*
+
+#### Using colour to map effects
+
+On the template:
+
+- Yellow = opportunities and benefits  
+- Red = risks and costs
+
+These might be connected - a benefit in one layer can create a risk in another.
+
+#### How to use it
+
+- Before decisions:  
+    - map potential effects to anticipate consequences  
+- To course-correct:  
+    - when something feels off, check whether your effects are matching your values  
+- To refine values:  
+    - if you keep seeing the same unintended consequences, your values might need updating!
+
+*We'll walk through a Baby Ghosts example (or presenter's example) so you can see this in action.*
+
+---
+
+### Activity: Identify one decision - 5 min
+
+Each studio identifies one upcoming **decision** they could run through either tool this week with their Peer Support.
+
+This doesn't need to be a big decision. Small decisions work well for practice.
+
+Share your decision in your studio channel before you leave today.
+
+---
+
+### Recap - 5 min
+
+**To recap:**
+
+- Start with your individual and collective values - talk them over  
+- Talk about the WHY before you get to the WHAT and HOW  
+- Use Layers of Effect to see if your impact is matching your values
+
+We've covered a lot of topics here, but they are all centred around the goal of making sure your values are more than just lip-service.
+
+---
+
+## Closing - 5 min
+
+*Which tool are you most curious to try?*
+
+---
+
+## Homework
+
+1. **Apply Layers of Effect to an upcoming decision** – Use the Miro template on your studio board. Walk through: what are the primary, secondary, and tertiary effects? Who gains, who pays, who's invisible but affected?
+
+2. **Work through Why/What/How with your Peer Supports** – Start with at least one value from your team's values map.
+
+3. **Discuss as a studio** – How often should you revisit your values and check whether your effects match your intentions?
+
+---

content/curriculum/Sessions/Session 4 – Decision-Making in Practice.md

@@ -0,0 +1,332 @@
+# Session 4: Decision-Making in Practice
+
+
+## Welcome
+
+- Slide: Tag Yourself
+
+---
+
+## Intro - 2 min
+
+You've identified your values and started making them actionable. But when the pressure is on and you need to make a call together, who decides? How? In traditional studios, the boss decides or the loudest voice wins. Cooperatives need different approaches that include everyone while still moving forward.
+
+This session is about noticing your *current* patterns and practicing alternatives. Before we can design governance structures (next session), we need to see clearly how decisions actually happen now.
+
+---
+
+## Check-in - 10 min
+
+Last session you practiced Layers of Effect on a decision. What did you notice when you tried to connect your values to a specific decision? Was it easier or harder than expected?
+
+---
+
+## Decision-making - 25 min
+
+### Who gets to raise issues? - 6 min
+
+The old way of making decisions is the boss decides for everyone, or majority rules. But coops use different approaches that include everyone while still moving projects forward.
+
+But before we look at different methods for decision-making, let's talk about **when** and**why** decisions need to be made.
+
+In traditional structures, only managers can put items on meeting agendas. Only certain people can say "we need to decide this." Everyone else has to hope someone with authority notices the problem.
+
+In a cooperative, **anyone affected by an issue** can bring it to the group. But we need systems so important things don't get lost and small things don't overwhelm us.
+
+**Activity: Private journaling (3 min)**
+
+- What decisions get made without asking anyone?  
+- What issues do you notice but can't formally raise?  
+- When do you wish you could say "hey, we should all talk about this"?  
+- What traits/behaviours get valued in your group? (e.g., fast processing, availability, wittiness, technical skills)
+
+Where do cooperative decision-making opportunities come from? From members raising issues. Here are some examples:
+
+- Proposals  
+    - *I think we should do X. Here's why and how. What does everyone think?*  
+- Check-ins
+    - *How is everyone feeling about Y? Should we address this formally?*  
+- Process intervention  
+    - *Can we try a different approach?*  
+- Values checks  
+    - *How do these options align with our values?*
+
+But **who** makes decisions? When determining who will make a decision, ask:
+
+- Who is most affected by that decision?  
+- Does it have far-reaching consequences for the entire cooperative (like a change to who can be a member), or does it mainly affect a specific discipline/person/team?
+
+---
+
+### Tool introduction: Informal Hierarchy Check-In - 5 min
+
+*inspired by Fuck Hierarchy! by [Yejin Lee](https://www.jeongllc.com/aboutyejin)*
+
+Studios should do a periodic check-in to assess how they are doing around informal hierarchy. These questions help you notice patterns before they become de facto process:
+
+**Who spoke most in our last meeting?** This reveals voice distribution - whose contributions dominate discussions.
+
+**Whose idea did we go with by default?** This reveals deference patterns - whose suggestions get adopted without much scrutiny.
+
+**Who knows how to do *X* that no one else knows?** This reveals knowledge concentration - where expertise creates dependency.
+
+**What happened last time someone disagreed?** This reveals dissent tolerance - whether pushback is welcomed or punished.
+
+**Whose schedule shapes our meeting times?** This reveals whose needs get centred - who the group accommodates and who has to adjust.
+
+You don't need to feel guilty if some of these questions point to you! For the group, it's important to *notice* patterns before they calcify.
+
+---
+
+### Decision-making steps - 7 min
+
+Whatever framework you use, cooperative decision-making involves choosing between options together. Consider these steps:
+
+1. Name the decision and who it affects. Be clear about what's actually being decided and whose voices need to be included.  
+2. Understand the context. What's happening? What do people feel and notice about this situation? *Emotions are rich information.*  
+3. Identify the underlying need. What are we actually trying to address here?  
+4. Generate options together. What approaches might work? Encourage unconventional (weird!) ideas. Notice who's contributing: Are the same people always first to speak? Whose ideas get picked up and built on?  
+5. Check alignment with your values. How do these options fit with who you want to be as a studio?  
+6. Evaluate consequences collectively. Who benefits, who's affected, what trade-offs exist? Notice whose preferences are shaping the conversation and whether anyone has gone quiet.  
+7. Decide using your chosen framework. *Name the method* (consent, consensus, etc.) before you begin. Before finalizing, pause and ask directly: "Does anyone have concerns they haven't voiced?" or "Is anyone agreeing just to move on?" Give time for people to respond, especially those who process more slowly or tend to stay quiet. Silence doesn't mean agreement.  
+8. Clarify implementation and revisit. Who does what? When will you check back to see if adjustments are needed?
+
+*Adapted from Effective Practices in Starting Co-ops*
+
+---
+
+### Handling dissent - 5 min
+
+When someone raises a concern late in the process, don't get frustrated that they are slowing the process down. *This is **super valuable** information!* Thank them for speaking up! It's not an easy thing to do, even for a contrarian (well, maybe).
+
+Then consider: Is this a clarification or modification that can be addressed quickly? Or does it point to something more fundamental that means the group isn't ready to decide? If the concern is substantial, revisit earlier steps (especially 2, 3, or 5).
+
+Watch for language like "I guess I can live with it" or "I don't want to hold everyone up," which show that someone is just giving in to move things along rather than really consenting. *A decision that leaves someone feeling steamrolled will cost more in trust and cohesion than the time it takes to slow down.*
+
+---
+
+## Frameworks - 14 min
+
+Different decisions call for different approaches. Here are five common frameworks:
+
+### Consensus - 7 min
+
+Everyone agrees that the selected option is the right option. Members can block a decision if it is not their top choice (even if they'd be ok with it).
+
+"It's important to remember that **no decision-making structure can prevent all conflict or power dynamics, or guarantee that we will never be frustrated or bored or decide to part ways.** But consensus decision-making at least helps us avoid the worst costs of hierarchies and majority rules, which can include abuse of power, demobilization of most people, and inefficiency. **Consensus decision-making** gives us the best chance to hear from everyone concerned, address power dynamics, and make decisions that represent the best wisdom of the group and that people in the group will want to implement." – Dean Spade, [*Mutual Aid: Building Solidarity During This Crisis (and the Next)*](https://theanarchistlibrary.org/library/dean-spade-mutual-aid#toc14)
+
+Consensus decision-making is the most effective way to make important decisions with small groups. The process requires direct participation and active listening from all involved and, when well facilitated, leads to better decisions and stronger commitment.
+
+**Core principles:**
+
+- All participants contribute  
+- Everyone's opinions are used and encouraged  
+- Differences are viewed as helpful rather than hindering  
+- Those members who continue to disagree after full discussion indicate that they are willing to experiment for a prescribed period of time  
+- Enough time will be spent that all voices are heard and understood before an effort to finalize a decision is made, however long that takes  
+- All members share in the final decision
+
+**Advantages:**
+
+- Members are more likely to support the decision  
+- Provides for a win-win solution  
+- Facilitates open communication  
+- Requires members to listen and understand all sides of the issue  
+- Sets the stage for action: Who, What, Where, When
+
+**Disadvantages:**
+
+- Takes more time in a group; the larger the group, the more time may be needed  
+- Trust is needed among members to encourage sharing  
+- Group leaders must use facilitation rather than control
+
+**Steps in facilitating consensus:**
+
+1. Describe and define the problem, situation, or issue  
+2. Brainstorm a list of alternatives without judging, discussing, or rejecting any ideas  
+3. Take only one idea from each person to start  
+4. Review, change, consolidate, rewrite, and set priorities as a group through discussion  
+5. Make a decision; when it's reached make sure it is written so that everyone can see it  
+6. Evaluate the results later - revise if needed
+
+*Source: Russ Christianson (Effective Practices in Starting Co-ops, p. 470\) and Washington State University Cooperative Extension*
+
+---
+
+### Consent - 5 min
+
+Consent helps us find an option that everyone is okay with, even if it's not their first choice. The decision statement must be carefully worded so that everyone is crystal clear on what they are consenting to.
+
+The question in consent is: "Is this good enough for now, safe enough to try?"
+
+This is different from consensus. In consensus, everyone must actively agree that the decision is the right choice. In consent, the bar is lower: No one has a paramount objection. You're asking "Can you live with this? Does it violate your values or cause harm you can't accept?" rather than "Do you love this?"
+
+Consent also protects against the opposite problem: Rigidity. When a group treats past decisions as permanent – "but we already agreed to make an RPG" – it can become impossible to adapt when things change. Consent-based decisions are explicitly *revisitable*. The question isn't just "can you live with this?" but also "can you live with this *for now*, knowing we'll check back?" If someone is blocking a revisit of an old decision, that's worth examining – are they protecting a genuine value, or has the original decision become an identity they can't let go of?
+
+Sociocracy is one approach to this. Sociocratic organizations use a peer governance system based on consent, where work is organized into semiautonomous small groups, known as circles. Sociocracy has a very specific formal structure for consent decision-making. We'll link to its process so you can check it out.
+
+[Consent Decision Making – Sociocracy 3.0](https://patterns.sociocracy30.org/consent-decision-making.html)
+
+Consent makes room for experimentation. If a decision doesn't work, you can always revisit it. This prevents analysis paralysis while still hearing everyone's concerns.
+
+---
+
+### Other frameworks - 2 min
+
+**Majority/democratic:** Each member votes, and the option with the most votes wins (simple majority, two-thirds, etc.). If your group uses formal voting, consider Democratic Rules of Order over Robert's Rules – same structure (chair, agenda, motions, votes) but without the procedural layers that create knowledge asymmetry and can be exploited as a power dynamic. Robert's Rules are arcane, parliamentary, and not appropriate for democratic organizations. Steer clear!
+
+**Delegation:** The member with the most expertise makes the decision – but how is this person determined? Through a decision!
+
+**Random chance:** When no one wants to decide, use a tool that generates a random yea or nay. A dice roll, coin flip – something like that.
+
+
+
+---
+
+## Meetings - 25 min
+
+Most meetings suck because they're designed hierarchically (one person talks, decisions happen elsewhere later). We're going to redesign them horizontally!
+
+### Preparation for an inclusive meeting - 3 min
+
+1. Use accessible tools for finding everyone's availability (Doodle, When2Meet, LettuceMeet, etc.)  
+2. Keep the meeting duration as short as you can while covering the agenda. Remember, participants' energy levels will fluctuate and you don't want to go so long that people get cranky. If you have too much ground to cover, consider moving some items to an asynchronous method like Slack threads or moving it to the agenda of a future meeting.  
+3. Prepare and share the agenda with time limits per item.  
+4. Assign roles and ensure they are rotated from previous meetings.
+
+Let's talk about meeting roles!
+
+---
+
+### Meeting roles - 10 min
+
+Meeting roles shouldn't be static. When the same person always facilitates, their style becomes "how we do meetings." Rotation (rotation! rotation! we can't emphasize this enough) builds shared skills and prevents informal hierarchy from becoming default process.
+
+#### Facilitator
+
+Guides the conversation and keeps things on track. The facilitator's job is to *help the group's wisdom emerge* rather than act as an expert on the topics. They should self-moderate their own input and be especially conscious of not being the strongest voice. 
+
+They also pay attention to group dynamics – such as, who hasn't spoken? Is someone checked out? Is tension building? (Some folks break this last responsibility into a*process/vibes observer* role, which may be especially helpful when trying out new decision-making methods.)
+
+**Tips:**
+
+- Before opening the floor, you can provide some quiet time for participants to write their thoughts down first  
+- Using "popcorn" style means anyone can jump in to share without a formal queue. Avoid selecting people to speak randomly – this can be stressful for those who do not wish to be called on. If multiple people indicate they want to speak, keep track of the queue and update the group.  
+- Share the floor. The facilitator makes sure that everyone gets heard and included, and no one dominates the discussion. They might intervene: "Jennie, we've heard a lot from you and I want to give some others a chance to share their perspectives."  
+- Provide regular process updates – that is, say what you're doing: "I'm going to take a few ideas, then we'll discuss"  
+- Listen actively and deeply  
+- Reflect back ideas that are shared and check with the speaker that you understand. This is an opportunity to synthesize what you just heard with the wider conversation to help everyone's understanding.  
+- Put ideas for later in the parking lot  
+- Red flags: rushing process and not tolerating awkwardness  
+- Check in with energy levels, especially when you see people are flagging. A 5- or 10-minute break might help perk everyone up to continue.  
+- Have prompts on hand if things go awry:  
+    - "I am noticing the tension. Should we pause and address that first?"  
+    - "I feel like we're going in circles/getting stuck – let's try a different approach."  
+    - "Let's pause for a moment and look at our process."
+
+#### Notetaker/minutes goblin
+
+Captures attendance, most important points, decisions made, and action items. Good notes include *who decided what* and *why*, not just discussion summaries. This creates accountability that doesn't depend on memory.
+
+#### Timekeeper/time baby
+
+Tracks time for each agenda item and gives warnings when time is running low. Helps the group decide whether to extend, table, or wrap up.
+
+Not every meeting needs all three roles, but rotating whatever roles you use prevents one person from becoming the de facto leader.
+
+---
+
+**HOT TIP: Not everything needs to be a meeting!** Meetings can also be a drain on a team. Consider when you can turn something into an asynchronous conversation or just have people assigned with tasks.
+
+---
+
+### The "genius" trap - 3 min
+
+When one person holds most of the knowledge, makes most of the creative calls, or is the only one who knows how something works, this is not a coop. You have a traditional studio with extra steps. This often emerges from who had time/was there first/whose skills were most visible at the start.
+
+Questions to help you spot role concentration:
+
+- who would we call if [X system] broke?  
+- whose absence would completely halt production?  
+- who "just handles" things that others don't fully understand?
+
+If the same name keeps coming up, you have a capacity risk *and* a governance risk.
+
+---
+
+### Role distribution != role rigidity - 3 min
+
+Cooperative roles should be:
+
+Visible
+
+- everyone knows who's responsible for what  
+- assigned through discussion, not assumption  
+- reviewed periodically as capacity and skills change
+
+This doesn't mean everyone does everything. Specialization is fine. The problem is when roles become permanent defaults that no one chose explicitly.
+
+---
+
+### Tracking and micro-documentation - 5 min
+
+*Nobody* loves tracking. (OK, maybe that biohacker guy Brian Johnson.) But when you don't document, institutional knowledge lives in one person's head, and that's how informal hierarchy gets baked in.
+
+Micro-documentation means capturing just enough that others can:
+
+- pick up where you left off  
+- understand why a decision was made  
+- notice patterns over time
+
+This doesn't require elaborate systems. It can be:
+
+- a shared doc/sheet where decisions get logged with date and rationale  
+- brief async updates ("here's what I did and why")  
+- meeting notes that include *who decided what*, not just discussion summaries
+
+**When you track decisions and contributions visibly, you create accountability that doesn't depend on memory or who speaks loudest.**
+
+---
+
+## Activity: Facilitation rotation practice - 15 min
+
+In groups of three, each take a turn as facilitator, participant, and observer.
+
+The facilitator will run a short discussion on a simple question (we'll give you one).
+
+**Sample questions:**
+
+- What game should we play together?  
+- What time during the week should we meet?  
+- Which two video game soundtracks should we swap?  
+- What type of team activity should we do?
+
+The observer watches for dynamics: Who spoke first? How did the facilitator handle silence? How was the decision reached?
+
+Rotate roles every 3 minutes.
+
+**Debrief (4 min):** What did you notice from each role? What was harder than expected?
+
+*Noticing dynamics is the most important thing here.*
+
+---
+
+## Closing - 2 min
+
+You've practiced frameworks and started noticing patterns – who speaks, who defers, whose defaults became the group's. These patterns *are* your governance, whether you've named it or not.
+
+Next session, we'll look at formal structures: How do you design governance that supports the decision-making practices you want and addresses the dynamics you noticed?
+
+---
+
+## Homework - 3 min
+
+1. **Practice one decision-making framework on a real decision** – Try consent or consensus on something that actually matters, even if it's small.
+
+2. **Map your current role distribution** – Where did each role assignment come from: Explicit decision, or implicit default?
+
+3. **Complete the Informal Hierarchy Check-In as a studio** – Work through the 5 questions together. Bring your observations to Session 5.
+
+4. **Notice this week: where do decisions happen?** – In meetings? DMs? Who's present?
+
+---

content/curriculum/Sessions/Session 5 – Coop Structures and Governance.md

@@ -0,0 +1,311 @@
+# Session 5: Coop Structures and Governance
+
+*Peer Supports: See **PS Guide: Session 5** for pre-session tasks.*
+
+---
+
+## Welcome
+
+- Slide: Tag Yourself
+
+---
+
+## Intro - 3 min
+
+Last session you practiced decision-making frameworks and noticed your current patterns. Those patterns *are* your governance, whether you've called it that or not.
+
+You don't need to incorporate in order to practice governance. But the structures you choose now will shape what kind of co-op you become. This session is about making that governance visible and intentional.
+
+## Check-in - 5 min
+
+*what did the informal hierarchy check-in reveal about your studio? anything surprising?*
+
+---
+
+## Coop vs Business - 10 min
+
+Before we talk about governance, let's quickly cover the legal landscape. You don't need to incorporate right now, but understanding the options helps you design governance that fits your eventual structure.
+
+### Common structures for game studios
+
+| Structure | Who owns it? | Who decides? | Who benefits? |
+| :---- | :---- | :---- | :---- |
+| sole proprietorship | One person | That person | That person |
+| Partnership | partners (often unequal shares) | usually based on ownership % | based on ownership % |
+| corporation | shareholders | board (elected by shareholders) | shareholders (via dividends) |
+| worker cooperative | workers (equal or near-equal) | workers (one member, one vote) | workers (based on labour, not capital) |
+
+### What makes a coop legally distinct?
+
+Three things:
+
+- Democratic control  
+    - One member, one vote. Not weighted by how much money you put in.  
+- Member ownership  
+    - The people who work there own it. Not outside investors, not founders who left years ago.  
+- Patronage returns - Surplus (profit) flows back to members based on their *labour contribution*, not their capital investment. Money follows work, not money.
+
+### The practical difference
+
+In a corporation, if you and two friends start a studio and one person puts in more money, they might own 60% and control major decisions. If you hire employees later, they're workers – not owners. If you sell the company, the original shareholders profit.
+
+In a worker co-op, every worker-owner has equal (or near-equal) say regardless of when they joined or how much they invested. If someone leaves, they don't keep ownership. New members buy in and become full owners.
+
+What aligns with your values and how you want to work together?
+
+### You don't need to rush
+
+Incorporation creates:
+
+- Legal protections (limited liability)  
+- Access to certain funding and tax benefits (e.g., OIDMTC in Ontario)  
+- An entity that can hold contracts, own IP, and survive individual members leaving
+
+Incorporation is not hard or expensive – which makes it tempting to treat as a milestone before the real work is done. But groups that rush to incorporate often find themselves still at step one two or three years later, because the relational and governance groundwork wasn't there yet.
+
+A few things worth knowing early: the Cooperative Corporations Act already covers a lot of ground. You don't need to replicate what the Act handles in your articles of incorporation, and over-specifying your objects or share structure in an attempt to "maintain control" is usually counterproductive – flexibility serves the co-op better as it evolves. Bylaws matter, but they're not the most important thing. Economic viability is. Spending too much time wordsmithing your bylaws is a distraction from the harder work of building sustainability.
+
+One more thing: Your legal advisors may not have co-op experience. Lawyers tend to default to conventional corporate structures, so seek out advisors who understand cooperative law, or at minimum, bring your own informed questions.
+
+The patterns you establish now – how you make decisions, how you handle money, how you share power – will shape what kind of co-op you become.
+
+***Today's focus: Governance practice, not legal paperwork.***
+
+### Quick check
+
+*By emoji reaction or in chat:*
+
+- How many of you have worked at a studio where you had no say in major decisions?  
+- How many have had equity or ownership in a company before?
+
+*no need to discuss - just noticing where we're starting from*
+
+---
+
+## Why cooperative structures? - 10 min
+
+The informal hierarchy check-in revealed patterns, right?
+
+Those patterns aren't problems yet. But under pressure informal patterns become cracks.
+
+Think: A funding deadline, a team member's life change, a game that's not working
+
+OK, we'll say it again: *Studios don't fail because of creative differences. They fail because of governance, conflict resolution, and communication misalignment.* The game was good. The team couldn't hold together long enough to ship it.
+
+You've already been practicing governance:
+
+- have you deferred a preference (e.g., working odd hours) to fit with the group?  
+- have decisions been made in DMs?
+- does one person hold knowledge others don't?
+
+Will you choose your governance structure together or let it emerge by default?
+
+You might think of governance as bureaucracy. But it's quite the opposite: It's making the invisible visible, the accidental intentional, the implicit explicit. It's building structures that enact your values so you have a clear path through the hard times.
+
+Not everyone in your studio needs to be a co-op nerd for your co-op to work. What matters is that your governance documents *encode your values into systems*. If your bylaws require transparent finances, transparency happens whether or not every member has internalized why it matters. If your decision-making process requires consent, no one can override the group even on a bad day. The documents you write this week are how your values work *almost automatically* even when people are tired and stressed.
+
+We want you to start making deliberate choices about how you'll work together, knowing you can revise as you learn.
+
+---
+## Case Study: Presenter's governance journey - 15 min
+
+---
+
+## Governance Models Overview - 15 min
+
+### Small studios (3-6 people): Collective Governance
+
+- All members make all major decisions together  
+- Rotate facilitation and administrative roles  
+- Use consent-based decision-making for most choices  
+- Monthly governance meetings for larger decisions  
+- Members are responsible for implementing their proposals
+
+### Small studios alternative: Advice Process
+
+You don't need their permission - just their input. Then you decide and own the outcome.
+
+- Anyone can make any decision, but must first seek advice from those affected and those with expertise. (You don't *need* agreement.)  
+- Helps work move faster without disconnecting knowledge from the coop; cuts down on meetings  
+- Requires high levels of trust and transparency
+
+Advice process fails if people skip the advice-seeking or if "advice" becomes de facto veto power.
+
+*From Buurtzorg and the "Reinventing Organizations" model*
+
+### Larger studios (7+): Circles (Sociocracy)
+
+The Circles model is essentially **sociocracy** (also called dynamic governance). If you want to research further, that's the term to search. This model helps you organize work at the most "local" level possible, by those directly impacted by the decisions.
+
+- Organize work into semi-autonomous circles (art, programming, bizdev)  
+- Each circle manages its own domain with clear boundaries  
+- Decisions within circles use ***consent*** process  
+- Circles link together through representatives who sit on multiple circles  
+- Larger decisions involving multiple circles invoke a representative Council  
+- Regular inter-circle coordination meetings
+
+[Sociocracy 3.0 (S3)](https://sociocracy30.org/) is an open-source, modular version - teams adopt patterns à la carte rather than implementing a whole system. Good if you want "some structure but not a rigid framework."
+
+You may have heard of [Holacracy](https://www.holacracy.org/). It is a more formalized, trademarked variant popularized by Zappos. More rigid and prescriptive, with detailed rules about roles and accountabilities. Overkill and overly corporate for you all.
+
+### Larger studios alternative: Board + Membership
+
+- All worker-owners are members  
+- Members elect a smaller board for ongoing governance  
+- Board accountable to membership through regular reporting  
+- Board sets conditions on membership and removal  
+- Board uses majority vote  
+- Clear division between governance (board) and operations (daily work)
+
+This model is closer to traditional nonprofit or corporate governance but with worker ownership. Can feel more familiar to people coming from conventional workplaces.
+
+But it's insufficient to just elect a board and call it democratic, if decisions have impact in a community that community needs to have a meaningful say in what those decisions are. It should go beyond "input" to actually having decision-making power.
+
+### Large studios alternative: DisCos (Distributed Cooperative Organizations)
+
+Developed by Guerrilla Media Collective. "Distributed" means distributed geographically (remote-first), distributed power (shared based on contribution), and distributed value (multiple types of work all count). Explicitly a cooperative, care-centred feminist economics alternative to DAOs.
+
+Gamma Space uses an adapted version of this model!
+
+- Value tracking across work types - distinguishes between *productive work* (the game),*care work* (team wellbeing), and *love work* (community, movement-building)  
+- Uses contributory accounting so invisible labour becomes visible and compensated  
+- Challenges assumptions about what counts as "real" work  
+- Federation over scaling - small nodes (max 15-20 people) federate together rather than growing one large organization  
+- Geared toward shared resources and open practices
+
+DisCOs build structures to account for work that often goes undervalued and unrecognized.
+
+Resources: [DisCO.coop](https://disco.coop) and the DisCO Manifesto
+
+Hot tip: Begin with collective governance or advice process, even if you think it's not the perfect fit. You can add complexity as you learn what you actually need.
+
+---
+
+### Decisions to clarify - 7 min
+
+Whatever model you choose, clarify:
+
+- Who can make spending decisions and up to what amount?  
+- What decisions require everyone vs. smaller groups?  
+- How do you change your governance structure as you grow?  
+- How do you document decisions and studio knowledge so it's not concentrated in one person?
+
+#### How do you add or remove members?
+
+This is often the hardest governance conversation. But you gotta have it before you need it.
+
+*Pre-formation studios often assume the original founders are permanent. But your governance should apply to everyone equally.*
+
+Adding members:
+
+- what's the process? who decides?  
+- is there a trial period?  
+- how do you onboard someone into your governance culture, not just your workflows?
+
+Voluntary departure:
+
+- what happens to their ownership stake?  
+- what about work in progress they were leading?
+
+Involuntary removal:
+
+- what are grounds for removal?  
+- who initiates/decides/what protections exist for the person being removed  
+- without a clear process, removal either doesn't happen (and resentment builds) or happens and it's a big ol mess
+
+#### Make accountability worth it
+
+If owning up to harm in your studio means losing everything – your community, your friends, your credibility, your income, your creative home – nobody will do it. They'll do anything to avoid that. You could end up spending months in a slow-motion crisis with no path out of it.
+
+When you're designing your conflict and removal policies, ask: Is it more worth it for someone to admit what they did than to lie about it? Is there a path back? Real consequences, real change required - but a path. If the only outcome of honesty is exile, you'll inevitably get dishonesty.
+
+This doesn't mean tolerating ongoing harm. Your process should distinguish between someone who is genuinely working to change and someone who is performing accountability while continuing the behaviour. The former needs support and real consequences; the latter needs a different response.
+
+#### The complexity of removing someone you care about
+
+The person you're removing is probably someone you care about. They're your collaborator and maybe your friend. The instinct to paint them as an irredeemable villain or monster makes the decision easier, but it's dishonest and in itself harmful to everyone. People who cause harm in your studio are human beings in your community - and yes, they hurt others, and that needs to be addressed. Holding both the care and the harm is one of the hardest tasks in cooperative work. Make room for that complexity rather than forcing everyone into a binary of good/bad.
+
+The person being removed may also be someone whose invisible labour has held things together. Community organizers, founders, people who did the unglamorous work of keeping things going when resources were scant - their contributions become very visible in their absence. A removal process that severs someone completely, without dialogue and without acknowledging what they built, both harms that person and damages the collective's relationship with its own history. Someone can take accountability for harm while the group still recognizes what they contributed. These ideas are both part of the truth and enable repair.
+
+Exile – total severance from community, communication, and support networks – is one of the most punishing things a group can do to a person, and it should be treated with that weight. If your removal process looks like excommunication, ask whether that's proportionate, whether it's actually serving the safety of the group, or whether it's being driven by urgency, fear, or the desire to make a painful situation disappear quickly. A process that centres care means making those decisions with enough deliberation, transparency, and humanity that everyone involved - including the person being removed - can see that the process was trustworthy.
+
+*you don't need to finalize these policies now. but you should know where your group is easily aligned vs. where you'll need more conversation.*
+
+---
+
+### Decisions under external pressure - 5 min
+
+What happens when a publisher wants an answer in 48 hours? When a grant deadline lands during a conflict or crisis? When a platform opportunity requires a yes or no right now?
+
+Think back to two weeks ago when we went over two scenarios and how you would make a decision as a studio. The focus was on returning to values. Governance can make sure you’re structuring that essential values work.
+
+The urgency of external pressure can break down democratic processes. OR, you might discover you never planned for this situation!
+
+Some things you could do:
+
+- Delegation with parameters  
+    - for opportunities under $x or commitments under y weeks, [person/role] can decide. anything bigger comes to the full coop.  
+- Emergency consent  
+    - we'll make a decision with whoever's available, then confirm or revisit at our next full coop meeting  
+- Defined response  
+    - we tell external parties we need [x days] to decide collectively. And if they can't wait, it's not the right fit
+
+It comes back to V A L U E S! And having a plan in place you've all agreed to ahead of time.
+
+*Think about past times when you've faced external deadlines. Who decided? Was everyone okay with that?*
+
+---
+
+## From patterns to structure - 10 min
+
+### Distributed capacity
+
+In Session 4 you noticed patterns through the Informal Hierarchy Check-In. So what governance structures would address what you noticed?
+
+Use these questions to connect your observations to design choices:
+
+1. Whose defaults have become the group's defaults?  
+    - Did everyone consent to that? What structure ensures future defaults are chosen collectively?  
+2. What knowledge is concentrated in one person?  
+    - What happens if they leave or burn out? How does your governance distribute capacity?  
+    - "Each historical moment of the organization should be carefully documented and archived... Investing in documentation also ensures that the power that comes from information is better distributed." -- [Solidarity Economy Principles](https://solidarityeconomyprinciples.org/)  
+3. Who can say no, and what happens when they do?  
+    - Does your structure make dissent safe and productive?  
+4. What rhythms and speeds does the group assume?  
+    - Who gets excluded by those assumptions? How do you build in flexibility?  
+5. How does accountability move?  
+    - Only from members to collective? Or in all directions?
+
+The patterns you noticed aren't problems to fix!
+
+They're information for design. Your governance should make the invisible visible and the accidental… intentional!
+
+---
+
+## Tool: Community Rule - 10 min
+
+[Community Rule](https://communityrule.info/) is a tool for documenting governance structures in plain language. We'll walk through the interface and show you an example from Gamma Space.
+
+Start drafting with your Peer Support this week, taking note of what fields the tool asks for and where you already have answers vs. where you need to chat more.
+
+---
+
+## Closing - 5 min
+
+You've drafted a governance structure based on what you've learned about your decision-making patterns. But governance doesn't exist in a vacuum. It shapes (and is shaped by) how you handle money.
+
+Next session, we'll dig into equitable economics: Transparent finances, compensation models, and profit-sharing. The governance you've designed will help you make those financial decisions together.
+
+*Think about: What's one aspect of governance your team hasn't discussed yet?*
+
+---
+
+## Homework
+
+1. **Start your Community Rule draft** – During your PS session this week, use the tool to document what you've decided so far and where the gaps are. Bring questions to next session.
+
+2. **Discuss financial sustainability with your studio** – What does financial sustainability look like for you personally? What would you need from this project? (Prep for Session 6.)
+
+3. **Personal reflection** – What financial information have you never been allowed to see at work?
+
+---

content/curriculum/Sessions/Session 6 – Equitable Economics.md

@@ -0,0 +1,253 @@
+# Session 6: Equitable Economics
+
+## Welcome
+
+Tag Yourself
+
+---
+
+## Intro – 5 min
+
+Last session you designed governance structures. Now we test them on the hardest topic: Money.
+
+In traditional studios, financial information is hoarded. If the boss says we can't afford raises, how do you know that's true if you don't have access to the books? If you've been the victim of the sudden shuttering of a studio, you probably didn't see it coming, because you never saw the real financial picture.
+
+Secrecy entrenches power. In a cooperative, we have the opportunity to bust this wide open.
+
+---
+
+## Check-in – 10 min
+
+Last session's homework asked you to discuss: *What does financial sustainability look like for you personally? What would you need from this project?*
+
+Anyone want to share what came up in that conversation?
+
+*And think about what financial information have you never been allowed to see at work?*
+
+---
+
+## Part 1: Where money comes from – 15 min
+
+We're going to talk about transparency and sharing in a bit. But we want to start with the good stuff!
+
+Where does money actually come from for game studios and creative cooperatives?
+
+Most sustainable studios don't rely on a single revenue stream.
+
+### Member contributions
+
+- Member shares – equity buy-in when you join  
+- Member loans – members lending to the co-op, sometimes with interest  
+- Sweat equity – labour contributed before there's money to pay wages
+
+### Grants and public funding
+
+- Arts councils – Ontario Arts Council, Canada Council  
+- Industry programs – Ontario Creates, Canada Media Fund, etc.  
+- Municipal and regional funds  
+- Project-specific grants
+
+### Revenue from work
+
+- Publisher advances and deals  
+- Platform funding – Epic MegaGrants, id@XBOX etc.  
+- Client work and contracts  
+- Direct sales  
+- Crowdfunding  
+- Service/contract work – porting, QA, art assets, sound design for other studios  
+- Adjacent creative work – animation, writing, interactive installations  
+- Knowledge work – workshops, speaking, consulting, teaching
+
+### Investment and loans
+
+- Impact investors (like Weird Ghosts and [others](https://gammaspace.slack.com/docs/T024FLYSV/F08HYF76NBV))  
+- Co-op development funds (CWCF's Tenacity Works, regional funds)  
+- Credit unions and community lenders  
+- Traditional bank loans (harder to access for co-ops)
+
+*Adapted from Effective Practices in Starting Co-ops*
+
+This needs to be a collective and intentional decision. Developing and maintaining these streams require time and effort that can eat into your actual game development.
+
+*Coops have different capital options than traditional startups.* Venture capital doesn't work for us – VCs want big returns on their investment and eventually an "exit" (sale), which conflicts with worker ownership. On the other hand, we have access to funding streams that prioritize social impact over profit maximization.
+
+Cooperation among cooperatives is one of the ICA cooperative principles we talked about a few weeks ago. When you do take on client or contract work, consider prioritizing work with other coops and solidarity economy organizations. This is a way we can build a "trade network" that helps everyone!
+
+So think about: What funding sources has your studio used or considered? What feels aligned with your values?
+
+---
+
+## Part 2: Financial transparency – 15 min
+
+### Why transparency?
+
+- Financial secrecy is a tool of control  
+- Open books = shared power  
+- When everyone understands the money, everyone can participate in real decisions
+
+### Basic practices
+
+- Share monthly financial summaries with all members  
+- Open-book policy (anyone can see the full accounts)  
+- Make all compensation transparent (everyone knows what everyone earns)  
+- Plan budgets collectively – this practice is sometimes called *participatory budgeting*, where members have real decision-making power over how money is allocated
+
+### Tips for accessibility
+
+- Use plain language – not everyone speaks accounting.  
+- Summarize number-dense spreadsheets ("we have 8 months of operating costs in the bank")
+- Create space for questions. There are no embarrassing questions about money – most of us were never taught this stuff.
+- Visual dashboards can help. Tools like [CoBudget](https://cobudget.com/) or [OpenCollective](https://opencollective.com/) make finances visible, or even just a shared spreadsheet
+
+### Tell the messy truth
+
+Transparency isn't just internal. When you're doing public-facing work like crowdfunding, devlogs, community updates, try to be honest about struggles, not just successes. When the story gets ahead of the reality, slow down and catch up.
+
+### Common resistance
+
+We have heard – what if competitors see our numbers?
+
+But for real – what's actually at risk versus what's just discomfort? Most studios aren't competing on secret financial information. Is this fear really about vulnerability?
+
+*Resource: [Seeds for Change – Finance](https://www.seedsforchange.org.uk/finance)*
+
+---
+
+## Part 3: Compensation models – 20 min
+
+SO! How do cooperatives pay people? There's no single right answer, but whatever you choose should be transparent and collectively decided.
+
+*we have tools to help you try out these models at [coop.love](https://coop.love)*
+
+### Models to consider
+
+*Equal pay:* Everyone earns the same hourly or monthly rate regardless of role.
+
+- Pros: Simple, values all contributions equally, prevents hierarchy creep  
+- Cons: Doesn't account for different needs or experience levels
+
+*Needs-based:* Pay is adjusted based on members' actual financial needs (rent, dependents, debt, etc.)
+
+- Pros: Addresses real inequity, mutual care in action  
+- Cons: Requires vulnerability and trust, can feel uncomfortable to discuss
+
+*Role-based:* Different rates for different roles or skill levels.
+
+- Pros: Familiar, can help attract specialized skills  
+- Cons: Can recreate the hierarchies you're trying to escape
+
+*Hybrid approaches:* Base rate + adjustments, or equal base with different hours allocated
+
+Whatever model you choose, *think about: What do we collectively believe is fair, and can we talk openly about it?*
+
+### Activity – 10 min
+
+In studio groups, discuss:
+
+- What feels fair to you?  
+- What would you need to know about each other to decide on a compensation model?  
+- What conversations would be uncomfortable, and what does that reveal?
+
+Share back with the group.
+
+---
+
+## Part 4: Profit-sharing basics – 20 min
+
+### What is profit-sharing in a coop?
+
+When the cooperative has surplus (revenue beyond expenses), how does it get distributed? This is fundamentally different from how corporations work.
+
+### Three types of money flowing to members
+
+*Wages:* Payment for work performed. This is an expense, not profit-sharing.
+
+*Patronage returns (or "dividends"):* Distribution of surplus based on members' contribution to the coop – usually measured by hours worked. This is what makes coops different: surplus flows to the people who created it, not to outside investors.
+
+*Member shares:* Your equity stake in the coop. Usually a fixed amount you pay to join, returned when you leave.
+
+### Common approaches to distributing surplus
+
+- *Equal split:* Divide surplus equally among all members  
+- *Hours-based:* Distribute based on hours worked since last distribution  
+- *Hybrid:* Some percentage equal, some percentage hours-based  
+- *Contribution-based:* Weighted by type of contribution (common in coops where some members bring capital, others bring labour)
+
+### When to distribute versus when to reserve
+
+This is a *values* conversation!
+
+- Build a reserve first. How many months of runway do you want before distributing anything? – there's no right answer.  
+- Distribute when you have genuine surplus, not just a good month  
+- Decide collectively if you want cash now or investment in the studio's future?  
+- Some coops allocate a percentage of surplus to a "collective account" for shared needs
+
+### Incorporation context
+
+Cooperative legislation is provincial in Canada, so the rules depend on where you incorporate.
+
+*Ontario:* Worker coops can distribute patronage returns to members based on their labour contribution. There's flexibility in how you structure this – you decide the formula in your bylaws.
+
+*Federal:* You can also incorporate under the Canada Cooperatives Act, which has its own rules.
+
+However you structure it, patronage returns flow to workers based on their labour – not to outside shareholders based on their investment. This is the legal mechanism that grounds worker ownership.
+
+### Discussion
+
+Any questions about how this would work for your studio?
+
+---
+
+## Part 5: Who owns what you make together? – 10 min
+
+We've talked about how surplus flows to members. Buuuut, before you can share surplus you need to decide *who owns* what you're creating together!
+
+In traditional studios, the company owns everything. Employees have no claim to their creative work. When the studio sells or shuts down, workers walk away with nothing.
+
+Cooperatives can do this differently with explicit decisions!
+
+### Questions to discuss as a studio
+
+1. Who owns the game?  
+    – the cooperative as an entity? individual members jointly? a mix?  
+    – if the coop owns it, what happens to that ownership if someone leaves?  
+2. What about work created before the coop formed?  
+    – if someone brings existing assets, code, or designs into the project, do they retain individual ownership or contribute it to the collective?  
+    – how do you value those contributions?  
+3. What happens if someone leaves mid-project?  
+    – do they retain any ownership stake in work they contributed to?  
+    – can they take "their" assets (character designs, code they wrote) with them?  
+    – what's the difference between leaving voluntarily vs. being asked to leave?  
+4. What happens if the studio dissolves?  
+    – who controls the ip? can one member buy out others?  
+    – what if you can't agree?
+
+*Not deciding* means you're going to default to whatever legal structure you eventually incorporate under. Worst case scenario is realizing too late that everyone's expectations were mismatched.
+
+### A note on sweat equity
+
+If you haven't started selling your game yet and members are contributing labour without pay, how does that translate to ownership?
+
+"Sweat equity" is complicated. Some coops track hours and convert them to ownership stakes. Others treat all founding members as equal regardless of hours contributed. However you do it, everyone needs to understand and agree to the approach.
+
+*Use your Peer Support session to start this conversation. You don't need answers yet – just notice where you're in agreement and where you're uncertain.*
+
+---
+
+## Closing – 5 min
+
+Financial conversations can be really difficult. They reveal vulnerabilities, and tensions about values, fairness, and trust. There's so much space for conflict to show up here.
+
+In the next session, we'll build tools for navigating disagreement constructively.
+
+Think about: *Is there a financial conversation your team has been avoiding?*
+
+---
+
+## Homework (with Peer Supports)
+
+1. **Discuss financial transparency** – What financial information would feel vulnerable to share? What would you need to feel safe sharing it? What have you never been allowed to see at a workplace – and what would have been different if you had?
+
+2. **Discuss compensation models** – What feels fair to you? Where do you notice tension between "fair" and "comfortable"? What do you need to know about each other's situations to decide together?
+
+---

content/curriculum/Sessions/Session 7 – Conflict Resolution and Collective Care.md

@@ -0,0 +1,365 @@
+# Session 7: Conflict Resolution and Collective Care
+
+*Peer Supports: See **PS Guide: Session 7** for pre-session tasks.*
+
+---
+
+## Intro – 5 min
+
+Last session we tackled the hardest topic: money. Financial conversations are often where conflict first shows up in a studio. If your compensation discussion went smoothly, great. If it got tense, you now have more information about your teammates!
+
+We've been taught that conflict means something is wrong. But in healthy cooperatives, disagreement is *valuable data* – it tells us there's an opportunity to create something better for everyone.
+
+Something to hold as we go through today: Many of us show up to cooperative spaces already scanning for signs we don't belong. We arrive hopeful, and then feel let down when something isn't perfect. This is a pattern shaped by a lifetime of not feeling belonging. Knowing this, we can design our studios and our conversations with more care.
+
+> Cooperatives don't eliminate conflict: they harness it. Conflict signals where values misalign or needs aren't being met. – Samantha Slade, *Going Horizontal*
+
+**Addressing conflict head-on is an act of care.** Avoidance lets harm fester.
+
+---
+
+## Check-in – 5 min
+
+What came up in your compensation models discussion from last session? Where did you notice friction? Or surprised by alignment?
+
+---
+
+## Part 1: Reframing conflict – 15 min
+
+### Conflict as care
+
+- Disagreement is DATA, not failure  
+- Addressing issues directly is caring – avoidance lets harm fester  
+- Healthy teams have conflict; unhealthy teams suppress it
+
+People who avoid conflict aren't being cooperative. They are invisibilizing their pain. And people who escalate every disagreement into combat are treating conflict as threat rather than neutral signal.
+
+In community listening projects across Western North Carolina, Cooperate WNC found that the biggest impediment to the success of collective projects was conflict – even more than money. *Even more than money.*
+
+Unresolved conflict drives people out entirely. Most people who leave cooperative or movement work do so because they are in pain because of conflict that was never addressed. They joined work they cared about, something went wrong, and the resulting loss of trust is what actually burns them out.
+
+### Conflict transformation
+
+One way to think about addressing conflict is as an opportunity for transformation, not just resolution.
+
+Traditional corporations just want conflict to go away so they can get workers back to their desks at maximum productivity. Conflict is a bottleneck to profits.
+
+But if we actually looked at the underlying sources of conflict, we'd have to acknowledge the systems that created it.
+
+> "A given **conflict is just a fruit on the tree of the underlying whole system** it came out of. Those root causes usually have to do with trauma, power structures, and the ways capitalism shapes our relationships. We don't want to just resolve conflicts and brush them under the rug. We want to see each one as a doorway into the underlying causes, so we can**transform them and create deeper trust** through the process." – Zev Friedman, Cooperate Western NC
+
+### Structural vs. interpersonal
+
+**Structural conflict:** Recurs no matter who's involved (keeps happening with different people); caused by governance gaps, power imbalances, unclear roles, resource scarcity.
+
+**Interpersonal conflict:** Communication can resolve it; misunderstandings, style differences, unmet expectations
+
+Many conflicts are both. The structural issue creates the conditions for interpersonal friction
+
+Fix the structure first – otherwise you're just managing symptoms.
+
+It's also useful to ask…
+
+- Is there a collective impact, or is it personal preference?  
+    – Helps determine urgency  
+- Is the concern evidence-based or speculative?  
+    – Shapes how you will respond
+
+Communication tools don't fix governance problems. If the structure is broken, no amount of "I statements" will help!
+
+#### Watch for the emotional-political conflation trap
+
+Before diagnosing a conflict as structural or interpersonal, check whether political language is standing in for emotional experience. We might be very good at naming the political or identity-based dimensions of a disagreement but much less practiced at naming the emotional dynamics underneath. When we're afraid or defensive, reaching for political framing can feel like solid ground – but it can also make repair harder.
+
+In your studio, someone might feel unheard in a creative decision and frame it as a power or equity issue. *Both might be true!* But if you skip the emotional reality and go straight to political framing, you make resolution harder. Try to name both.
+
+### Some truths of conflict
+
+1. Just talking about conflict can create conflict.  
+2. Working through conflict takes time. Sometimes *lots* of time.
+3. Conflict *will* happen. We promise. Even if you're best friends.
+
+### Multi-directional accountability
+
+In cooperatives, accountability runs in multiple directions. Members are accountable to each other and to the collective – but the collective is also accountable to each member. This is different from traditional workplaces where accountability only flows upward to bosses.
+
+"Holding someone accountable" sounds like something that happens *to* a person who messed up. We all come together and make them answer for what they did. But you can't actually hold someone accountable. Accountability is a process someone *engages in by choice*.
+
+What you *can* do is create the conditions where accountability is possible. Can someone in your studio admit they messed up without it being a catastrophe? Is there enough trust that people will be honest about impact without it turning into a dehumanizing pile-on? Do people feel seen enough as real, full humans that they can hear hard feedback without shutting down or peacing out?
+
+One thing we've learned from community work is that accountability requires specificity. You can't take responsibility for unspecified offences – it's impossible to address "you caused harm" when no one will tell you what you did. Vague accusations invite shame, defensiveness, capitulation – and none of those are repair. If your studio's process asks someone to account for their behaviour, it needs to name – clearly and specifically – the behaviour being addressed.
+
+The other thing is that your processes only work if people actually use them. Organizations can have beautiful conflict resolution policies on paper and then bypass them entirely when things get real. When that happens, the processes weren't truly aligned with the group's actual values. If you build accountability structures, commit to using them even (especially) when it's uncomfortable or inconvenient. An organization that abandons its own processes in a crisis is telling its members that those processes were never real.
+
+When we approach conflict as a structural/movement condition rather than an individual failing, the question shifts from _who is the problem?_ to _what is our structure doing that's making this harder?_ What would need to change so people could actually be honest about the harm they've caused?
+
+[*Solidarity Economy Principles*](https://solidarityeconomyprinciples.org/theme-collective-care-relationships-and-accountability/)
+
+---
+
+## Part 2: Common Conflicts in Game Studios – 15 min
+
+**1. Workload and contribution**
+
+- resentment over inequitable workloads  
+- "they're not pulling their weight" (but have you actually talked about capacity?)  
+- different definitions of "done" or "good enough"
+
+**2. Creative direction**
+
+- disagreement over game vision or scope  
+- one person's idea keeps "winning"  
+- feeling unheard in creative decisions
+
+**3. Money and compensation**
+
+- discomfort with pay transparency (or lack of it)  
+- disagreement over how to split revenue or profit  
+- different financial needs creating different risk tolerances
+
+**4. Roles and power**
+
+- original founder holds informal power  
+- unclear decision-making authority  
+- someone taking on a "manager" role without agreement
+
+**5. Communication and presence**
+
+- different expectations for availability/response time  
+- remote work misunderstandings  
+- someone going quiet instead of raising concerns
+
+### Noticing informal power (without it being "conflict")
+
+Think back on the Informal Hierarchy Check-In from Session 4… those same questions apply here:
+
+- whose idea did we go with by default?  
+- who gets deferred to?  
+- whose schedule shapes our meeting times?
+
+*Noticing is not accusing.* Pointing out "hey, we've defaulted to jennie's preferences three times now" isn't conflict. The goal is *noticing before patterns calcify*.
+
+You can name power accumulation without it being a fight. If you can't – your coop might not have enough capacity for handling conflict.
+
+### Discussion
+
+*do any of these feel familiar? are they structural, interpersonal, or both?*
+
+---
+
+## Part 3: Tools for Conflict – 15 min
+
+"We live in a society based on **disposability**. When we feel bad, we often automatically decide that either we are bad or another person is bad. Both of these moves cause damage and distort the truth, which is that we are all navigating difficult conditions the best we can, and we all have a lot to learn and unlearn. If we want to build a different way of being together in groups,**we have to look closely at the feelings and behaviours that generate the desire to throw people away**. Humility, compassion for ourselves, and compassion for others are antidotes to disposability culture. Examining where we project on others and where we react strongly to others can give us more options when we are in conflict. Every one of us is more complex and beautiful than our worst actions and harshest judgements. Building compassion and accountability requires us to take stock of our own actions and reactions in conflict, and seek ways to treat each other with care even in the midst of strong feelings." – Dean Spade, ["Practicing New Social Relations, Even in Conflict"](https://francesslee.medium.com/practicing-new-social-relations-even-in-conflict-dean-spade-54d4a60fcfed)
+
+### Loving Justice framework
+
+Before speaking, ask: Is it Brave? Kind? Honest? Humble?
+
+### Feedback is a gift
+
+This sounds like a platitude, but it's a real perspective shift. When someone gives you feedback, they're telling you *how to take better care of them* and how to make your system more functional. They're giving you information you didn't have.
+
+> "The shift is from perceiving feedback as threat to perceiving feedback as power. It's hard – especially if your pattern is defensiveness. But people who stay in cooperative work long enough often describe a moment when this actually flipped for them." – Zev Friedman, Cooperate Western NC
+
+### Behaviourally-specific feedback
+
+Sometimes feedback comes in very ugly wrapping – that doesn't mean there's not a gift inside.
+
+[TODO-IMAGE-03: Intent/Behaviour/Impact illustration from Connect (Bradford & Robin) – recreate or source]
+
+When two people interact, there are three realities:
+
+1. Intent (Person 1's reality): Their needs, motives, emotions, intentions  
+2. Behaviour (Common reality): Tone, words, gestures, facial expressions – what actually happened  
+3. Impact (Person 2's reality): Your reactions and emotions
+
+Each person can only know 2 of these realities. You know the behaviour you observed and the impact on you.
+
+What we think about others’ intentions is only a hunch. And in any case, the problem is usually with a person’s behaviour, not their intentions.
+
+Stay on your side of the net. Moving beyond the 2 realities you understand makes the interaction accusatory.
+
+"you did x **because you don't respect me**" crosses the net. "when x happened,**i felt disrespecte**d" stays on your side.
+
+#### What counts as behaviour?
+
+Behaviour is something you can point to – words, gestures, even silence. A useful test: *If people were shown a video of the interaction, would they agree they saw the same behaviours?*
+
+Be specific. "You dominated the discussion" is a judgment based on a series of behaviours. "You spoke for 10 of the 15 minutes" is observable. The more specific you are, the harder it is for the other person to deny.
+
+### Why this works
+
+1. It is indisputable  
+2. It leads to the other party explaining their intentions  
+3. Focusing on behaviour avoids the problem of too much non-specific feedback being useless or destructive  
+4. All behaviourally specific feedback is **positive**  
+    1. behaviour is something we can change  
+    2. affirmative = “positive” and developmental = “negative”  
+5. All behaviourally-specific feedback is **data**, and more data is better than less.  
+    1. Feedback given with the intention of being helpful is always positive
+
+*Adapted from Connect: Building Exceptional Relationships with Family, Friends, and Colleagues by David Bradford Ph.D. and Carole Robin Ph.D.*
+
+### Stay with your truth
+
+What's the part of you that's saying "no"? That's pushing back? Can you speak from that place?
+
+"A part of me doesn't want to be here because..." "I'm afraid to have this conversation because..."
+
+Conflict is telling us if there is a problem or a need not being met. Hold onto that while holding onto someone else's truth.
+
+### Before you raise an issue
+
+Two things to watch for: shame responses (collapsing into "I'm a terrible person" instead of attending to the other person's experience – name it when you see it), and clarity about what you actually observed vs. interpreted. Before starting a conversation, get clear on: what specific behaviour did I observe? What "no"s are coming up for me? What's my part in this? What do I actually need?
+
+*For deeper reading on shame, accountability, and conflict: [Building Accountable Communities](https://bcrw.barnard.edu/building-accountable-communities/) – Dean Spade, Mariame Kaba, and BCRW.*
+
+---
+
+## Part 4: Window of Transformation – 10 min
+
+Timing matters:
+
+Is this person able to hear feedback right now? Are *you* able to give it?
+
+The "Window of Transformation" is an embodied conflict response model developed by Kai Cheng Thom, inspired by Dan Siegel and Pat Ogden's "Window of Tolerance." It maps different emotional states and responses to conflict based on nervous system activation.
+
+[TODO-03: Insert Window of Transformation graphic here after import]
+
+### The zones
+
+**Destructive (High Activation)**
+
+- Fight/flight responses, overwhelmed, panicked, enraged  
+- Attacking the other person or attacking the relationship  
+- "It's me or them, and I choose me"
+
+**Window of Transformation (Optimal)**
+
+- Hearing and integrating feedback with curiosity and compassion  
+- Stretched, challenged, expanding the edge of emotional capacity  
+- Able to hold boundaries while staying connected  
+- "I can honour your truth and honour mine"
+
+**Performative (Low Activation)**
+
+- Prioritizing maintaining relationship over integrity  
+- Overwhelmed, insecure, deceiving self or other to "appease"  
+- "Giving in to get along"
+
+**Fragile/Collapse (Very Low Activation)**
+
+- Collapsing into shame and blame, feeling victimized  
+- Stuck or immobilized, "freeze"  
+- Unable to engage at all
+
+### Using this framework
+
+You're not going to be able to stay in the Window of Transformation permanently! Your goal is to *notice* when you've left it and make choices accordingly.
+
+if you're in the Destructive zone: this is not the time to have the conversation – step away. Take a break.
+
+if you're in the performative zone: you might agree to things you don't actually consent to
+
+if you're in fragile/collapse: you need support, not a conflict conversation.
+
+Practice noticing where others are. If someone is clearly activated or shut down – leave some space.
+
+> "One thing that is surprising and challenging about the emotional dynamics of conflict is that we do the most harm to others when we are feeling aggrieved, victimized, left out, and/or resentful. It’s counterintuitive because those are the moments when we are focused on what others did wrong and how we are hurting. But those are the times we are most likely to do something harmful, like go and write the really messed up email to somebody, treat somebody with a cold shoulder, gossip negatively about people in our group or about another group in town, post a bunch of stuff on Instagram that’s really inflammatory, or violate someone’s privacy." – Dean Spade, "Navigating Conflict in Movement Spaces" (Nonprofit Quarterly)
+
+The moments you ***feel most justified*** are the moments you're most likely to cause harm. If you're feeling like the wronged party, that's exactly when to pause and ask a trusted person whether your planned response is the right scale.
+
+---
+
+## Activity – 10 min
+
+Here are some example scenarios:
+
+- So-and-so keeps talking over me in meetings  
+- One person keeps having to answer emails and is left out of game dev chats  
+- Another *small* conflict. (Although conflict has a way of bubbling up and becoming giant).
+
+### Discussion
+
+- is this structural, interpersonal, or both?  
+- using behaviourally-specific feedback: what would you actually say? (stay on your side of the net – what you observed, what impact it had)  
+- apply the Loving Justice questions (Brave? Kind? Honest? Humble?)  
+- what would make this issue easier to raise?  
+- notice what zone you're in
+
+---
+
+## Escalation as Care – 10 min
+
+Escalation is NOT failure! it's recognizing that some conflicts *need more support* than a 1:1 can provide.
+
+### Levels of escalation
+
+#### Direct conversation
+
+Talk to the person yourself. Use the tools we just practiced – behaviourally specific feedback, staying on your side of the net, checking what zone you're in before you start.
+
+#### Escalate bandwidth
+
+Escalate the bandwidth of the channel – if you’re on Slack asynchronous text, move to Slack synchronous text at a planned time. From synchronous chat to an audio Huddle, audio to video. *Credit: [Joshua Vial](https://joshuavial.com/loomio-conflict/)*
+
+#### Bring in a third party
+
+a trusted person who can facilitate – not to judge or decide, but to help both people hear each other. This could be another studio member, a Peer Support, or someone outside the studio you both trust.
+
+#### Formal process
+
+Use your documented conflict resolution policy. This is for when informal approaches haven't worked, when the conflict affects the whole studio, or when someone needs formal protections.
+
+Often formal conflicts trace back to unintegrated objections: concerns that were raised but never properly addressed. Preventing this requires actually working through tensions when they come up.
+
+*The goal isn't to always end up at the formal process. You just want to have it so everyone knows it exists. This can make informal resolution easier.*
+
+We'll share Baby Ghosts' conflict resolution policies and procedures as a template you can adapt. It includes: who initiates the process, what documentation happens, timelines, and what happens if resolution isn't reached.
+
+- Resource: [Baby Ghosts Conflict Resolution Procedures](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Procedures/Conflict+Resolution+Procedures)
+
+---
+
+### Trust comes from repair, not avoidance
+
+The Gottman Institute found that couples don't build trust by avoiding conflict. They build trust by having conflict and then repairing. The repair is what demonstrates: You matter to me enough that you're worth repairing with. I'm going to do the work.
+
+The same is true in cooperative work. Being willing to risk rupture, and then showing up for repair – that's what creates the trust. "Oh, you really did have my back when it mattered. You really were willing to receive feedback."
+
+>"People who stay put in conflict rather than run away are signalling they're ready for deeper work." – *Zev Friedman, Cooperate Western NC on John M. Gottman Ph.D., The Science of Trust*
+
+### Hot tips
+
+- Have a policy and procedures in place *before* your next crisis  
+- You can use Baby Ghosts' template as a starting point, but collectively review and modify it to your specific values, needs, and context  
+- Every member should be intimately familiar with these documents  
+- Know who is responsible for supporting members in conflict  
+- operationalize your values around conflict resolution by including it in your budget, reserving time in retreats and meetings, and signing up for relevant training.  
+- Practice on the small stuff. Don’t wait for a crisis. Every small repair is a rehearsal for the harder conversations. If you can’t talk about someone consistently showing up late to meetings, you definitely can’t talk about power dynamics or compensation disputes. Start where it’s low-stakes.
+
+Soul Fire Farm, an agricultural coop in New York, uses a peer-to-peer "Real Talk" process to give direct feedback. We'll share the link: [Soul Fire Farm Real Talk](https://agriculturaljusticeproject.org/toolkit/resources/relations/soulfire-real-talk/). This is a great framework if you want to build in regular feedback on a regular basis.
+
+---
+
+## Closing – 5 min
+
+*"Deescalate all conflict that isn't with the enemy." -- Margaret Killjoy*
+
+You've now built tools for governance, decision-making, financial transparency, and conflict. That's a lot. And next session is our last! CRY
+
+Some of these conversations may have been uncomfortable. You might be still thinking about things that came up this week.
+
+we'll step back and assess what you've created together. what's working/fragile/what comes next after this program ends?
+
+*between now and then: If hard conversations came up this week, don't let them drift away. Use your Peer Support session to keep working through them.*
+
+---
+
+## Homework
+
+1. **Name one avoided tension** – What conflict or tension has your studio been avoiding? It doesn't have to be big – small avoidances are good to examine too. What makes it tough to bring up? Can you practice raising it?
+
+2. **Review the conflict resolution template together** – Read [Baby Ghosts' conflict resolution policy](https://publish.obsidian.md/baby-ghosts-corp-docs/Public/Policies/Conflict+Resolution+Policy). As a studio, discuss: what would you adapt for your context, and what's missing for you?
+
+---

content/curriculum/Sessions/Session 8 – Self-Evaluation and Pathways.md

@@ -0,0 +1,140 @@
+# Session 8: Self-Evaluation and Pathways
+
+## Welcome
+
+- Slide: Tag Yourself
+
+---
+
+## Intro - 5 min
+
+This is the last session. Wahoo! Where did the time go?!
+
+Last week we talked about conflict. Some of you may have had difficult conversations since then. That's the good stuff, as eileen would say. It's okay if things feel unfinished or messy. You don't have to have it all figured out by now. We hope you feel you have the tools and the trust to keep figuring it out together.
+
+What happens next is going to be harder than the program. You'll ship a game, or you won't. Money will come in, or it won't. Life will get busy. And the governance practices you've built over these weeks can quietly erode if you stop doing them.
+
+You might skip a governance meeting because you're crunching… then another. Someone starts "just handling" the finances because it's easier than showing someone else how to do it. Six months later someone asks "why are we even a co-op?" and no one has a good answer. This is the most common way cooperatives fail.
+
+The post-program supports we're about to talk about exist to keep up your momentum and help you build your collaborative muscles - and remember the “why.”
+
+And today we pause to reflect on what you've built and where you're headed. We have two assessments - individual and studio - to help you see how far you've come and clarify your next steps.
+
+And then we'll celebrate as a group!
+
+---
+
+## Check-in - 5 min
+
+*What has shifted for you since Session 0?*
+*Has your emotional connection to the studio changed over the program?*
+
+---
+
+## Self-assessment overview - 5 min
+
+It's easy to get into a groove and forget to check in with yourself. But clarity of self-reflection makes you a better collaborator. Most of the work is making the time and space to sit with your thoughts before writing them down. That's what prevents decisions made in haste or fear and builds intentional practice instead.
+
+We have two assessments for you today. The first is personal and private – just for you. The second is collective – you'll complete it as a studio, and Baby Ghosts will review it to understand where you're at and how to support you going forward. This is also important feedback for us, so please be honest about what worked and what didn't.
+
+---
+
+## Personal self-assessment - 10 min
+
+**This is private.** Baby Ghosts won't see it. Your studio won't see it unless you choose to share.
+
+This helps you get a clearer sense of your personal and professional baseline. Be on the same page with yourself before you meet with your team. Where have you grown? Where do you still feel uncertain? What do you need from your collaborators that you haven't asked for yet?
+
+[TODO-06: Link to assessment form when ready. Tracked in Asana.]
+
+---
+
+## Studio self-assessment - 10 min
+
+**This is collective.** You'll complete it together as a studio, and Baby Ghosts will review it to understand where you're at and how to support you.
+
+The template is on your studio Miro board. You'll rate where your studio is on each of seven areas using this scale:
+
+1. **Considering/Reflecting** – You've thought about it individually but haven't discussed it as a team yet.
+2. **Discussing Collectively** – You're talking about it together but haven't made decisions.
+3. **Brainstorming** – You're actively generating ideas and exploring options.
+4. **Sifting/Sorting** – You're narrowing down, making choices, working toward alignment.
+5. **First Draft of Documentation** – You have something written down – a policy, a process, a shared agreement.
+
+The seven areas map to the arc of this program:
+
+1. Values, purpose & alignment
+2. Governance
+3. Decision-making & meetings
+4. Equitable economics
+5. Conflict & repair
+6. Program reflection
+7. What's next
+
+Be honest with each other. A "2" in conflict resolution after eight weeks means you know where to focus. This assessment also helps you understand if your studio is ready to continue together, to pause, or to part ways. All of these are valid outcomes.
+
+---
+
+## What's next - 15 min
+
+Two questions to start: *What do you want to focus on as a studio going forward? What's your plan for revisiting your governance and values after the program ends – and who's responsible for scheduling it?*
+
+### Stay connected: Ghost Guild
+
+When the program wraps up, your weekly Peer Support sessions end – but your Peer Support isn't going anywhere. They're still part of the community, and many are happy to hear from you as you hit milestones or run into challenges.
+
+Going forward, your home base for support is the Ghost Guild – Baby Ghosts' alumni community. Program alumni are automatically enrolled. Membership includes free access to talks and workshops, community building with solo devs, early access to resources, and opportunities to become a Peer Support or contribute to the knowledge commons.
+
+### Keep practicing
+
+Build in a revisit of your values and governance documents. Quarterly is ideal, twice a year at minimum. Put it on the calendar before you leave today. Ask: are we still practicing what we said we would? Where have we drifted? What needs updating? The studios that stay cooperatives are the ones that keep asking these questions.
+
+Build in a self-accountability practice too. Values drift can happen quietly. To prevent it, make a regular habit of asking yourself: Did my choices today align with who I want to be? This can be as simple as a five-minute reflection at the end of the week, or a quick message to a collaborator: "Hey, I was short with you yesterday. That wasn't who I want to be. Sorry." You've been building this muscle all program. Stay strong! – put it alongside your governance review on the calendar.
+
+### Upcoming workshops
+
+We offer standalone workshops throughout the year on topics we've introduced here – and some we haven't had time to cover in the program. These are included with Ghost Guild membership or available for public registration. Past and upcoming workshops include: Legal Structures & By-Laws, Business Planning, Grantwriting & Alt Funding, Social Impact, Advanced Governance, Miro / Tools Workshop, Why We're Here: Telling Your Studio's Story, and Process Development.
+
+### Interested in becoming a Peer Support?
+
+Some of you may be interested in supporting future cohorts as a Peer Support. This is a paid role and a meaningful way to build capacity in the community – you already know firsthand what studios go through, and that experience is exactly what makes a great PS.
+
+Here's what the role involves: you'd attend all program sessions alongside your assigned studios, facilitate weekly peer support meetings with one studio, and participate in PS training before the cohort starts. It's approximately 4-6 hours per week during the 10-week program. If you're someone who found yourself energized by the collaborative work, who notices group dynamics, and who cares about holding space for others – this might be a great fit. Talk to us after the session or reach out anytime.
+
+### Incorporation
+
+If your studio is ready to incorporate as a cooperative, we can point you toward resources and service providers who understand cooperative structures. We don't provide legal advice, but we can help connect you with people who do.
+
+And a reminder: you don't have to incorporate to work cooperatively. Many studios practice cooperative values and governance long before – or without ever – filing incorporation papers. The practices matter more than the paperwork.
+
+[TODO-14: Develop resources, service providers, and readiness assessment. Tracked in Asana.]
+
+---
+
+## Collaborative Zine Making - 35 min
+
+*Eileen leads this activity.*
+
+---
+
+## Closing - 5 min
+
+You're about to re-enter an industry that defaults to hierarchy. Lawyers will draft conventional corporate structures. Funders will ask for a single point of contact. Publishers will want to know who's in charge. Your own teammates – under pressure – may reach for the familiar. This is expected. It's how we've learned to operate.
+
+There is no self-made entrepreneur. Everyone is embedded in community – cooperatives just make that explicit. You've spent eight weeks building the muscle to do that together. Keep using it.
+
+_What's something you're proud of from the program?_ _What conversation did you have that you wouldn't have had otherwise?_
+
+---
+
+## Homework
+
+1. **Complete your personal assessment** – Do this before your studio meets. This is private, just for you.
+
+2. **Complete your studio assessment together** – Meet as a studio and work through the template on your Miro board. This comes back to Baby Ghosts so we can understand where you're at and how to support you going forward.
+
+[TODO-04: Add due dates for assessments]
+
+And stay in touch. You're part of this community now. 👻👻👻
+
+---

scripts/import-curriculum.js

@@ -0,0 +1,297 @@
+#!/usr/bin/env node
+
+/**
+ * Import Baby Ghosts Coop Foundations Curriculum into Outline wiki.
+ *
+ * - 9 session pages → top-level in "Cooperative Foundations" collection
+ * - 10 PS Guide pages → nested under "Peer Support Playbook" parent doc
+ * - Cross-links added between paired session/PS Guide pages
+ *
+ * Usage:
+ *   OUTLINE_URL=https://wiki.ghostguild.org OUTLINE_API_TOKEN=<token> node scripts/import-curriculum.js
+ */
+
+import fs from "fs/promises";
+import path from "path";
+import { fileURLToPath } from "url";
+
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+
+const OUTLINE_URL = process.env.OUTLINE_URL;
+const OUTLINE_API_TOKEN = process.env.OUTLINE_API_TOKEN;
+const RATE_LIMIT_MS = 200;
+
+const SESSIONS_DIR = path.resolve(__dirname, "../content/curriculum/Sessions");
+const PS_GUIDES_DIR = path.resolve(__dirname, "../content/curriculum/PS Guides");
+
+if (!OUTLINE_URL || !OUTLINE_API_TOKEN) {
+  console.error("Error: OUTLINE_URL and OUTLINE_API_TOKEN env vars are required.");
+  process.exit(1);
+}
+
+// --- API helper (same pattern as migrate-content.js) ---
+
+async function outlineApi(endpoint, body) {
+  const res = await fetch(`${OUTLINE_URL}/api/${endpoint}`, {
+    method: "POST",
+    headers: {
+      "Content-Type": "application/json",
+      Authorization: `Bearer ${OUTLINE_API_TOKEN}`,
+    },
+    body: JSON.stringify(body),
+  });
+
+  if (!res.ok) {
+    const text = await res.text();
+    throw new Error(`API ${endpoint} failed (${res.status}): ${text}`);
+  }
+
+  return res.json();
+}
+
+function delay(ms) {
+  return new Promise((resolve) => setTimeout(resolve, ms));
+}
+
+// --- Session files in order ---
+
+const SESSION_FILES = [
+  "Session 0 – Kickoff + Onboarding.md",
+  "Session 1 – Coop Principles and Power.md",
+  "Session 2 – Shared Purpose and Alignment.md",
+  "Session 3 – Actionable Values and Impact.md",
+  "Session 4 – Decision-Making in Practice.md",
+  "Session 5 – Coop Structures and Governance.md",
+  "Session 6 – Equitable Economics.md",
+  "Session 7 – Conflict Resolution and Collective Care.md",
+  "Session 8 – Self-Evaluation and Pathways.md",
+];
+
+// --- PS Guide files with explicit titles ---
+
+const PS_GUIDE_FILES = [
+  {
+    file: "pre-program-onboarding-and-prep.md",
+    title: "Pre-program: Onboarding and Prep",
+    sessionIndex: null, // no cross-link pair
+  },
+  {
+    file: "0-kickoff-onboarding.md",
+    title: "PS Guide: Session 0 — Kickoff + Onboarding",
+    sessionIndex: 0,
+  },
+  {
+    file: "1-coop-principles-power.md",
+    title: "PS Guide: Session 1 — Coop Principles and Power",
+    sessionIndex: 1,
+  },
+  {
+    file: "2-shared-purpose-alignment.md",
+    title: "PS Guide: Session 2 — Shared Purpose and Alignment",
+    sessionIndex: 2,
+  },
+  {
+    file: "3-actionable-values-impact.md",
+    title: "PS Guide: Session 3 — Actionable Values and Impact",
+    sessionIndex: 3,
+  },
+  {
+    file: "4-decision-making-in-practice.md",
+    title: "PS Guide: Session 4 — Decision-Making in Practice",
+    sessionIndex: 4,
+  },
+  {
+    file: "5-coop-structures-governance.md",
+    title: "PS Guide: Session 5 — Coop Structures and Governance",
+    sessionIndex: 5,
+  },
+  {
+    file: "6-equitable-economics.md",
+    title: "PS Guide: Session 6 — Equitable Economics",
+    sessionIndex: 6,
+  },
+  {
+    file: "7-conflict-resolution-collective-care.md",
+    title: "PS Guide: Session 7 — Conflict Resolution and Collective Care",
+    sessionIndex: 7,
+  },
+  {
+    file: "8-self-evaluation-pathways.md",
+    title: "PS Guide: Session 8 — Self-Evaluation and Pathways",
+    sessionIndex: 8,
+  },
+];
+
+// --- Content helpers ---
+
+/** Strip the H1 line from markdown content. */
+function stripH1(text) {
+  return text.replace(/^# .+\n+/, "");
+}
+
+/**
+ * Remove PS reference lines that appear near the top of session pages.
+ * Handles both italic and non-italic variants:
+ *   *Peer Supports: See **PS Guide: Session N** for pre-session tasks.*
+ *   Peer Supports: See **PS Guide: Session N** for pre-session tasks.
+ * Also removes an empty "## Pre-session" heading left behind.
+ */
+function stripPsReference(text) {
+  // Remove the PS reference line itself
+  let result = text.replace(
+    /^\*?Peer Supports: See \*\*PS Guide: Session \d\*\* for pre-session tasks\.\*?\n+/m,
+    ""
+  );
+  // Remove empty "## Pre-session" section (heading followed only by --- or whitespace)
+  result = result.replace(/^## Pre-session\n+(?=---)/m, "");
+  return result;
+}
+
+// --- Main ---
+
+async function main() {
+  // ============================================================
+  // Phase 1: Find existing collection and parent document
+  // ============================================================
+
+  console.log("Phase 1: Finding collection and parent document...\n");
+
+  const { data: collections } = await outlineApi("collections.list", { limit: 100 });
+  const collection = collections.find(
+    (c) => c.name.toLowerCase() === "cooperative foundations"
+  );
+  if (!collection) {
+    console.error('Error: Collection "Cooperative Foundations" not found.');
+    process.exit(1);
+  }
+  console.log(`  Collection: ${collection.name} (${collection.id})`);
+  await delay(RATE_LIMIT_MS);
+
+  const { data: searchResults } = await outlineApi("documents.search", {
+    query: "Peer Support Playbook",
+    collectionId: collection.id,
+    limit: 5,
+  });
+  const parentDoc = searchResults.find(
+    (r) => r.document.title === "Peer Support Playbook"
+  );
+  if (!parentDoc) {
+    console.error('Error: Document "Peer Support Playbook" not found in collection.');
+    process.exit(1);
+  }
+  const parentDocId = parentDoc.document.id;
+  console.log(`  Parent doc: Peer Support Playbook (${parentDocId})\n`);
+  await delay(RATE_LIMIT_MS);
+
+  // ============================================================
+  // Phase 2: Import 9 session pages
+  // ============================================================
+
+  console.log("Phase 2: Importing session pages...\n");
+
+  const sessions = []; // { id, slug, title }
+
+  for (const file of SESSION_FILES) {
+    const raw = await fs.readFile(path.join(SESSIONS_DIR, file), "utf-8");
+
+    // Extract H1 as title
+    const h1Match = raw.match(/^# (.+)$/m);
+    const title = h1Match ? h1Match[1] : path.basename(file, ".md");
+
+    // Strip H1 and PS reference from body
+    let body = stripH1(raw);
+    body = stripPsReference(body);
+
+    const { data: doc } = await outlineApi("documents.create", {
+      title,
+      text: body.trim(),
+      collectionId: collection.id,
+      publish: true,
+    });
+
+    sessions.push({ id: doc.id, slug: doc.url.split("/doc/")[1], title });
+    console.log(`  ✓ ${title}`);
+    await delay(RATE_LIMIT_MS);
+  }
+
+  // ============================================================
+  // Phase 3: Import 10 PS Guide pages
+  // ============================================================
+
+  console.log("\nPhase 3: Importing PS Guide pages...\n");
+
+  const psGuides = []; // { id, slug, title, sessionIndex }
+
+  for (const entry of PS_GUIDE_FILES) {
+    const raw = await fs.readFile(path.join(PS_GUIDES_DIR, entry.file), "utf-8");
+
+    // Strip H1 from body
+    const body = stripH1(raw);
+
+    const { data: doc } = await outlineApi("documents.create", {
+      title: entry.title,
+      text: body.trim(),
+      collectionId: collection.id,
+      parentDocumentId: parentDocId,
+      publish: true,
+    });
+
+    psGuides.push({
+      id: doc.id,
+      slug: doc.url.split("/doc/")[1],
+      title: entry.title,
+      sessionIndex: entry.sessionIndex,
+    });
+    console.log(`  ✓ ${entry.title}`);
+    await delay(RATE_LIMIT_MS);
+  }
+
+  // ============================================================
+  // Phase 4: Add cross-links
+  // ============================================================
+
+  console.log("\nPhase 4: Adding cross-links...\n");
+
+  for (const psGuide of psGuides) {
+    if (psGuide.sessionIndex === null) continue; // skip pre-program
+
+    const session = sessions[psGuide.sessionIndex];
+    if (!session) {
+      console.error(`  ✗ No session found for index ${psGuide.sessionIndex}`);
+      continue;
+    }
+
+    // Update session page: prepend PS Guide link
+    const { data: sessionDoc } = await outlineApi("documents.info", { id: session.id });
+    await delay(RATE_LIMIT_MS);
+
+    const sessionCrossLink = `> **Peer Supports:** See [${psGuide.title}](/doc/${psGuide.slug}) for your role during session and this week's studio support meeting.\n\n`;
+
+    await outlineApi("documents.update", {
+      id: session.id,
+      text: sessionCrossLink + sessionDoc.text,
+    });
+    console.log(`  ✓ ${session.title} → ${psGuide.title}`);
+    await delay(RATE_LIMIT_MS);
+
+    // Update PS Guide page: prepend session link
+    const { data: psDoc } = await outlineApi("documents.info", { id: psGuide.id });
+    await delay(RATE_LIMIT_MS);
+
+    const psCrossLink = `> **Session content:** See [${session.title}](/doc/${session.slug}) for the full curriculum.\n\n`;
+
+    await outlineApi("documents.update", {
+      id: psGuide.id,
+      text: psCrossLink + psDoc.text,
+    });
+    console.log(`  ✓ ${psGuide.title} → ${session.title}`);
+    await delay(RATE_LIMIT_MS);
+  }
+
+  console.log(`\nDone. ${sessions.length} sessions + ${psGuides.length} PS Guides imported.`);
+}
+
+main().catch((err) => {
+  console.error("Import failed:", err);
+  process.exit(1);
+});