Team Charters

One charter per Linear team: what the team is for, what belongs on it, how its work flows, and the paste-ready configuration for Linear team settings.

The cross-team rules (routing tiebreaks, labels, funding lifecycle, cycle rollover) live in the Linear operating model. Charters describe one team each and never contradict the operating model; if they drift, the operating model wins and the charter gets fixed.

Team	Key	Cycles	Charter
Product	PRD	2-week	product.md
Research	RESR	Long, one theme per cycle	research.md
Community	COM	2-week	community.md
Growth	GROW	None (pipeline-driven)	growth.md
Marketing	MAR	None (brief-driven)	marketing.md

Each charter carries:

• Purpose — the team description, kept word-for-word identical to the Linear team settings description.
• What belongs here / what doesn't — routing examples and graduation rules.
• Workflow states — the deliberate state set and why.
• Cycles — whether the team runs cycles and at what rhythm.
• Evaluator panel — who signs off scoped briefs for this team.
• Templates — which Linear templates this team uses.
• Surfaces — the Discord channels and routines that cover this team.