Literature synthesis
Pull twenty papers on a question, cluster them by claim, surface where the field agrees and where it disagrees. The Researcher reads, the Summariser distils, the Writer threads — every claim back to the page it came from.
Drop a file, ask a question, get a chart. No formulas required.
Native dataset-driven analysis with the Data workspace — pull a file into the question, ask in plain English, get a chart that points back at its source.
Pull twenty papers on a question, cluster them by claim, surface where the field agrees and where it disagrees. The Researcher reads, the Summariser distils, the Writer threads — every claim back to the page it came from.
Draft the methods section for a study from prior protocols and the question at hand. Comparable methods get pinned next to yours; the workshop drafts the rationale for each design choice; you keep the editorial call on what survives the review.
Hand the workshop a dataset and a question. The Analyst writes the cleaning step, runs the model, drops the chart. Code, output and rationale live next to each other in a notebook a peer can re-run.
Start from a paper that matters. Follow what cites it, what it cites, what it argues against. The workshop holds the graph in your head — surfacing the lineage of an idea across years of literature without losing the thread.
The shape of the work when two papers point in opposite directions and the answer has to defend itself.
What this isn'taskFinz is not a journal, a peer-review system or a citation manager that owns your bibliography. We don't replace Zotero, the IRB or the editorial board. The workshop produces the notebook, the synthesis, the merged draft you would otherwise stitch together across five tools and a folder of PDFs. The defensible version of the answer; you still own where it lands.