---
name: research-brief
description: Turn a loose question into a sourced brief where every claim carries a citation and a confidence tag, and unverifiable threads become open questions instead of smooth prose. Use for technology comparisons, market scans, "what's the current state of X" questions, and any answer that will drive a decision.
---

# Research Brief

## When to use

- "Should we use X or Y?" technology comparisons
- "What is the current state of Z?" landscape questions
- Any answer someone will rely on for a decision

## The format

### Question

Restate the question in one sentence, scoped tight enough to answer.

### Findings

One subsection per finding. Every claim gets:

- **Source** - a real, retrievable citation with its date
- **Confidence** - one of:
  - HIGH: primary source, recent, directly on point
  - MEDIUM: secondary source, or primary but dated/partial
  - LOW: single weak source, inference, or conflicting reports

A claim without a source does not go in Findings. It goes in Open
Questions.

### Open Questions

Everything you could not verify, stated as plainly as the findings.
"Unknown" is a valid and valuable result. Never launder an open
question into a finding by softening the wording.

### So what

Two or three sentences: what this means for the decision at hand. If
the evidence is too thin to recommend, say that.

## Rules

- Prefer primary sources: official docs, release notes, pricing pages,
  the repo itself. Blogs citing blogs is a trail to follow, not a
  source to cite.
- Record retrieval dates. Prices, limits and terms rot fast.
- When sources conflict, report the conflict with both citations.
  Never average away a disagreement.
- Keep the brief under one page of prose. If it is longer, the question
  was not scoped tightly enough.

## Hard boundaries

- No claim without a citation or a confidence tag.
- No hiding low-confidence claims in confident prose.
- No answering what was not asked - park adjacent discoveries in a
  one-line "also seen" note.
