A research-note template you can copy

Structure is the cheapest way to make research readable. Copy the skeleton below into the editor and fill each section. Delete anything that doesn't apply — a short, honest note beats a padded one.

The template

## Summary

One paragraph. State the claim and the takeaway in plain language, as if the
reader will only read this section. What did you find, and why does it matter?

## Background

What's already known, and the specific gap you're addressing. Link prior work.
Keep it to what a reader needs to follow you — not a full literature review.

## Method

Exactly what you did, in enough detail that someone else could repeat it:

- Setup: models, datasets, tools, hardware.
- Procedure: the steps, in order.
- What you controlled for, and what you didn't.

Pin versions, data, and seeds. "Latest" is not a version.

## Results

What actually happened. Lead with the headline number or finding, then the
detail. Include:

- The main result, with a table or figure if it helps.
- Variance across seeds/runs — not a single lucky run.
- What *didn't* work. Negative results are results.

## Limitations & next steps

Where this could be wrong, what it doesn't cover, and what you'd do next. Name the
failure modes before a reviewer does.

## References

Links to prior work, code, data, and artifacts.

How to use it

• Fill Summary last. It's easiest to write once the rest exists.
• Cut ruthlessly. If a section is one honest sentence, leave it one sentence.
• Show your work. A link to a repo or a config is worth a paragraph of prose.
• Match the checklist. Before submitting, run the draft past the rigor checklist in the contributor guide.

When it's ready, submit it for review from the editor. A maintainer will read it and either publish it or send back notes.