Get people ready to participate, and keep them supported once they do.

Key: COM · Cycles: 2-week · Panel: afo, nansel, matt

Purpose

<<<<<<< HEAD Linear team description (paste verbatim — the settings field caps at ~255 characters, and this version fits):

Accepted community work: cohorts, onboarding, support coverage, gatherings, and member coordination. Output is people ready to participate. Product changes graduate to Product; campaigns and creative go to Marketing.

The fuller statement: the output of this team is people ready to participate — onboarded operators, supported members, sessions that happened.

Use this text verbatim as the Linear team description (new team, no description set yet):

Accepted community work: cohorts, onboarding, support coverage, gatherings, and member coordination. The output is people ready to participate: onboarded operators, supported members, sessions that happened. Product changes graduate to Product; campaigns and creative go to Marketing.

origin/main

What belongs here

• Cohort building and readiness (PGSP first-cohort readiness COM-8, Builder Space kickoff prep COM-9).
• Garden and operator onboarding and engagement (commitment-pooling operator onboarding COM-3, garden survey COM-7).
• Support coverage as a continuous role (tracked as a monthly coverage issue, see the compensation playbook).
• Gatherings, workshops, and community events.

What doesn't

• The product features a cohort needs → Product.
• Announcements, campaign content, and creative assets for community pushes → Marketing.
• Partner or funder relationship management → Growth.

Workflow states

Backlog · Todo · In Progress · In Review · Done · Canceled · Duplicate

• Deliberately no Triage: community work is created on purpose (from calls, cohort plans, or briefs), not harvested from raw reports. If community intake ever starts landing here automatically, add Triage then.
• No state changes needed; this set matches the live Linear configuration.

Cycles

2-week cycles (cycle 1 started 2026-07-16), sharing Product's rhythm so cohort work and the product work it depends on can be planned together.

Evaluator panel

afo, nansel, matt. Roster is confirmed in the Evaluator Panels Linear Document.

Templates

Templates live globally at the workspace level (steward decision 2026-07-18), not per team — create and apply them from linear-templates.md. This team's everyday shapes:

• Brief — the default for scoped community work (a survey, an onboarding push, an event).
• Continuous role (a Linear Document, not an issue) — support coverage and other ongoing arrangements.

Surfaces

• Discord: #community (weekly synthesis excerpt, community coordination).
• Routines: delivery-hygiene, weekly synthesis.
• Common labels: activity:community, protocol:* of the product the work supports (for example protocol:pgsp for cohort work, protocol:green-goods for garden onboarding).