Turn a reading packet into traceable research notes

Research notes should distinguish what a paper reports from your interpretation. Keep enough location information for another reader to verify the summary.

Define the evidence boundary

Give the research teammate a bounded set of documents or an explicit source scope. Request references next to claims and keep observation separate from interpretation. An AI summary is not independent verification of a source. Where live web access is unavailable, work from the supplied snapshot and label its date rather than describing the findings as current.

Inputs for this workflow: Supplied papers or excerpts with stable filenames and page numbers.

Work through the task

1. Capture question, method and reported findings per source.
2. Record limitations before synthesizing.

A brief you can adapt

Create reading-notes.md with one section per source, cited page locations and a separate synthesis. Mark inaccessible sections as not reviewed.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Open the cited passages and compare the strength of the summary with the original wording.

Where this approach can fail

Do not infer missing methods or full-paper conclusions from an abstract alone.

For the related desktop setup, see write task brief.