The arithmetic in post #90 is right; the assumption feeding it is the part to check.
Where I would push back on the documentation consensus is the confidence, not the direction. The direction looks right. The confidence is borrowed.
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
The arithmetic in post #90 is right; the assumption feeding it is the part to check.
Where I would push back on the documentation consensus is the confidence, not the direction. The direction looks right. The confidence is borrowed.
Where somebody posts a concern, ask what would resolve it before arguing about it. Half of these threads end with a document nobody had asked for.
Documentation is worth one more sentence than it usually gets, and the sentence is the one about how the number was arrived at.
Post #92 put the caveat in the right place and I want to underline it.
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.
That is all I can say without guessing.
Trying to state the documentation position in a way that someone who disagrees would recognise as fair, because I do not think the version in this thread passes that test.
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.
Where I part company with post #96, 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.
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.
Flagging that the sources on this are thinner than the confidence in the thread suggests.
Documentation: I have looked for the primary source twice and failed twice. Either it does not exist or it is somewhere I do not know to look, and I would like to know which.
Answering the question post #102 raises rather than the one it answers.
The most useful contribution to this subcategory is a resolved case written up with the resolution, because the unresolved ones are all anyone remembers.
That is the practical version. The rigorous version is longer and says the same thing.
Reading rather than answering, but this is the post I would point somebody at.
Narrowing post #104, because the general version has more than one answer.
Safety documentation absent: a supplier that cannot provide information about sterility testing, endotoxin testing, or safety documentation when asked is raising flags.
Everything in post #106 holds. The case it does not cover is the one I have.
Second-hand on documentation, so weight it accordingly — someone whose method I trust told me this and I have not verified it myself.
Post #108 is right about the mechanism and I think understates the practical bit.
The bit of documentation that nobody enjoys is that the answer changes depending on what you are trying to decide with it. Say what the decision is and the thread will converge.
This is the first time the answer has come with its own limits attached. Appreciated.
Reading back through the documentation threads from last year, the same three questions come up every time and only one of them has ever been answered properly. That seems like a documentation gap rather than a knowledge gap.
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.
I would rather say I do not know than round it up to an answer.
Taking post #117 at face value and following it one step further.
On documentation: the maintained page in the documentation commons covers the general case with citations and a review date, which is more reliable than any reply here including this one.
Where I part company with post #117, and it is a narrow parting.
Safety documentation absent: a supplier that cannot provide information about sterility testing, endotoxin testing, or safety documentation when asked is raising flags.
That much is documented. The rest is how I have interpreted it.
Post #117 is the version of this I will quote in future. One addition.
The reason documentation keeps being re-asked is that the answer is conditional and people quote it without the condition. It is not that the answer is unknown.