Growth

Fund the guild: run the grant pipeline and the partnerships behind it.

Key: GROW · Cycles: none (pipeline-driven) · Panel: afo, matt

Purpose

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

The guild's funding and partnership pipeline: prospects, drafts, submissions, active awards, reporting, and BD. Lifecycle lives on funding labels; every issue has a next action and deadline. Award-funded delivery is filed on Product and linked. ======= Use this text verbatim as the Linear team description (new team, no description set yet):

The guild's funding and partnership pipeline: grant prospects, drafts, submissions, active awards, reporting, and BD follow-through. Lifecycle is carried by funding labels, and every issue names its next action and deadline. Delivery unlocked by an award is filed on Product and linked.

origin/main

What belongs here

• The entire grant lifecycle, in every state: prospects (GROW-1, GROW-3, GROW-4), drafting, submitted, and active awards (GROW-13, Octant Epoch 12). One issue per opportunity, Grant: title, one funding:* label mirroring the lifecycle.
• Partnerships and BD follow-through.
• Funder-facing reporting and impact evidence coordination (the Impact Reporting project spans this team).

What doesn't

• The delivery an award funds → Product, linked back to the award issue here.
• Campaign creative for funding pushes (an Octant/Artizen campaign like MAR-12) → Marketing, linked, never duplicated.
• Research that informs a proposal → Research, unless it exists only to draft the proposal (then it stays on the grant issue).

Workflow states

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

• Pipeline stage is the funding:* label, not the state. States describe whether someone is actively working the opportunity; funding:prospect → drafting → submitted → active-award describes where the opportunity is. Keep both honest.
• The pipeline view is a saved view grouped by funding:* label (see the UI checklist; the old "Grant Scouting" project is retired, do not resurrect it).
• Deliberately no Triage: the grant-scout routine files prospects directly with the label and a decision-needed block. No state changes needed; this set matches the live Linear configuration.

Cycles

None. Funding work is deadline-driven (program deadlines, epochs, rounds), not cycle-driven. Due dates and the pipeline view replace cycle planning; the delivery-hygiene routine chases past-due and stalled owned issues here like everywhere else.

Evaluator panel

afo, matt. This is the thinnest panel; add a third member when one re-engages. 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:

• Grant — Opportunity · Fit · Evidence · Status · Decision needed. Title Grant: {Program}, one funding:* label, ai:routine when routine-authored.

Surfaces

• Discord: #funding (grant-scout digest, funding coordination).
• Routines: guild-grant-scout (files and dedupes the pipeline weekly), delivery-hygiene (non-funding BD issues only; the grant pipeline itself is grant-scout's turf), weekly synthesis.
• Common labels: funding:* (the lifecycle axis), activity:capital (monetization work), protocol:* of the product being funded.