Posting this under the heading it deserves: Documentation that appears only after payment Everything below is what sits behind that.
Proposing that Documentation deserves a maintained page rather than a recurring topic, and drafting the skeleton here so that the argument about scope happens before the writing rather than after.
What I think belongs on it, what does not, and the three claims that would need a citation each.
Picking up the opening post: that is the part I would want checked first.
What I would tell a new member reading about Documentation for the first time: the confident posts are not the reliable ones, and the reliable ones are longer.
Documentation quality as a signal: a supplier that reports method identifiers, distinguishes specification from result, and states the counter-ion form is telling you something about systems behind the document. A certificate that is a number and a signature tells you less.
Worth saying I have only my own numbers here, and n is small.
Confirming post #4 from a second method, which matters more than confirming it from a second person.
Exaggerated claims without documentation: every compound has limits. No peptide is "100% pure" because purity is measured to finite precision. A supplier claiming implausible perfection without backing evidence is overreaching.
The short answer was in the first line; everything after is the working.
I had written a reply contradicting post #2 and deleted it. Here is what survived.
Where the same certificate image appears with different lot numbers, that is a documentation finding worth reporting with the images attached.
I have seen it go both ways, which is why I hedge.
Documentation sits at the boundary between what this community can usefully discuss and what it cannot, and I think it falls on the discussable side, narrowly.
An update on my earlier Documentation post: the pattern held for another six weeks and then stopped, which I did not predict and cannot explain.
Documentation was covered in the wiki last year and the page has a review date on it, which is a better starting point than my memory of a thread.
Confirming post #9 from a second method, which matters more than confirming it from a second person.
Nothing here should be read as an accusation against a named company, and the guidelines exist so that reports remain reports.
I would be glad to be shown a cleaner way of putting this.
This is the sort of exchange that makes the archive worth searching.
Where I part company with post #13, and it is a narrow parting.
The guidelines draw that line for a practical reason as much as a fair one: reports accumulate into something useful and allegations do not.
Post #13 is the version of this I will quote in future. One addition.
Practical experience of Documentation, offered as one case with the conditions stated, not as a general finding. Conditions first, because they are what make it interpretable.
What I would check first on Documentation is whether the thing being measured moved or whether the way of measuring it moved. Those look identical in a graph.
Patterns that reliably precede a problem: underdosing (less active material than stated, documented by independent testing), mislabelling (wrong compound, wrong strength, or wrong batch on the label), and failure to provide documentation when asked.
I would put the burden of proof on the interesting explanation, not the dull one.
I had read the opposite somewhere and cannot now find where, which tells me something.
I have been on both sides of the Documentation argument in this category within eighteen months, which should tell you how strong the evidence for either side is.
Adding a small correction to the Documentation summary above rather than a disagreement with it. The substance holds; one of the figures is out by a factor that matters.
Unresponsiveness: a supplier that does not reply to reasonable requests for documentation or clarification is showing you something about how they operate.
Filing this under things that are true until someone shows me otherwise.
One caution on Documentation: everything above assumes the underlying documentation is what it claims to be. That assumption is doing real work and is rarely stated.
Bookmarking this. I will come back when I have something worth adding.
I read post #24 twice before replying, because I had assumed the opposite.
A certificate that reports a specification in the result column is a documentation defect, and it is a defect people should be able to recognise without it being called anything worse.
I would rather be precise about what I do not know than vague about what I do.
Picking up post #26: that is the part I would want checked first.
The strongest single signal available cheaply is what happens when you ask a technical question. A quantitative answer inside a working day is difficult to fake at scale.