Method Section Writer

The method section has one job: give the reader enough understanding to evaluate whether the claimed results are plausible and, in principle, to reproduce the work.

It is not a complete implementation guide. It is not a tutorial on all the components the method builds on. It is the minimal formal description needed to understand what is new and why it should work.

The two failure modes

Too dense: a wall of notation introduced all at once, multiple sub-components presented at the same abstraction level, equations without motivation. The reader can follow each line but cannot see the idea.

Too vague: prose that describes what the method does without saying how. "We encode the input using a contextual representation" is not a method — it's a description of the output. A reader cannot reproduce this or evaluate whether it's novel.

The target: present the key idea with enough precision that a skeptical reviewer can check whether the contribution is real.

Workflow