We publish the method. What we do at each stage, why, what has to be true before the work proceeds, how a claim is graded, and what would stop us. That is a methods section, and it is what a reader needs in order to judge whether a finding can be trusted. Without it, “we were rigorous” is just a word we chose.
We do not publish the implementation. The retrieval prompts, which models run which lanes, the extraction schemas, the structure of the claim database, the audit scripts. That is a lab notebook. No journal asks for one and no serious reader expects it.
The distinction is not a hedge. Anyone can make cola. The recipe is not what makes the chef, and the same knife chops a salad or skins an animal.
A competitor could adopt every step on this page tomorrow. They would still hold zero published error rates, zero calibration data, and no record of what they predicted against what subsequently happened.
The asset is not the technique. It is the history the technique produces: an accumulating database of claims and the sources they rest on, a public error‑rate record that gets longer every time we publish, and first‑party outcome data from our own engagements and deployments. Those take years, and they cannot be acquired by reading a web page.
Which is exactly why we can afford to be generous with the method.