Answer the questions the guild needs answered before it builds.

Key: RESR · Cycles: long, one theme per cycle · Panel: afo, coi, matt

Purpose

<<<<<<< HEAD Linear team description (unchanged from the live configuration; it already fits the ~255-character field):

Use this text verbatim as the Linear team description (unchanged from the live configuration):

origin/main

Accepted investigations: research tasks and partner or data inquiries answered before we build. The output is a decision-ready artifact, a memo, taxonomy, readiness plan, or a clear no-go, not code. Implementation graduates to Product.

What belongs here

• Impact methodology and framework work (the Greenpill Impact Framework refresh, evaluator flows, evidence standards).
• Partner and data investigations (Silvi, Locale, environmental and energy data inputs) before any integration is committed.
• Architecture and readiness briefs that precede implementation commitment.

What doesn't

• Implementation → Product (graduation is the point).
• Grant prospecting and drafting → Growth (even when research-flavored; the funding:* lifecycle owns it).
• Speculative ideas that haven't crossed the research acceptance bar → stay in Discord or Drive memos.

The acceptance bar, in short: specific surface or question, a next action more concrete than "investigate this", repeated signal or partner need, and small enough to track without becoming open-ended R&D.

Workflow states

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

• Triage holds inbound research signal that cleared the bar but hasn't been shaped into a brief.
• In Review is the peer-review step before an artifact is accepted.
• No state changes needed; this set matches the live Linear configuration.

Cycles

Long cycles (roughly monthly), each focused on one theme (currently "Q3 July — Methodologies & Commitments Alignment"). Accepted research either fits the active theme or waits for the next cycle; research is not judged on Product's two-week rhythm.

Evaluator panel

afo, coi, 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 research shape (Output · Scope · Done when), with Artifact children only when a piece fans into several outputs.

Surfaces

• Discord: #research (discussion; the automated Saturday synthesis is retired, research movement now appears in the weekly synthesis digest).
• Routines: delivery-hygiene (owned and dated work, scope hygiene), weekly synthesis (research block).
• Common labels: activity:research, activity:architecture, protocol:* of the product the research serves.