Course 0 · Lesson 4 · Members
How to label an observation
The structured report form, taught before anyone files one.
18+ · No peptide sales · No medical advice
1. Label it or it becomes a plan in disguise
Freeform chat turns observations into dosing and sourcing talk. The structured report form is the culture. Observation is not a recommendation. Completing this lesson does not authorize a use.
2. Why freeform fails
A paragraph that mixes what someone noticed with how much, how often, how to prepare it, or where to get it is no longer an observation. It is plan language. Moderators return that for edit. This lesson teaches the fields so the return is predictable.
3. Field-by-field walk
These are the site’s report fields (strategy grammar). There is no field for amount. There is no field for a shop. There is no “would I recommend.”
- Compound as labeled — the name as stated on the vial or box, not “the real X.”
- Context — in your own words (for example a training block; concurrent changes as yes/no plus whether discussed with a clinician). Not a medication-list dump.
- Duration band — days / weeks / months. Not a calendar plan.
- Noticed — what changed that you can name.
- Not noticed — what did not show up.
- Confounders — other things that moved (preview; deepened in Lesson 5).
- Uncertainty — required. One honest sentence.
- Source label — firsthand / paper / clinician conversation / other non-shop hearsay. A shop tip is not evidence of an effect. Factual shop reports belong on Vendor Watch when that form is open — not as Experience-drawer proof.
Good pattern: “Compound as labeled: [name on label]. Duration band: weeks. Noticed: sleep felt deeper some nights. Not noticed: no change in training recovery I can separate from a lighter block. Confounders: training volume dropped. Uncertainty: I cannot tell which change mattered. Source: firsthand.”
Bad pattern (return): “Here is [amount]. Buy from [source request]. Anyone else stacking this?”
4. Error states
Amount language in Noticed → return for edit.
Sourcing language anywhere → remove or return; it does not belong in an observation.
Advising another member what to take → remove.
Skipping Uncertainty because you “felt sure” → return; uncertainty is required.
5. Source labels — what each allows you to claim
- Firsthand — what you personally noticed under conditions you can name.
- Paper — a published finding you are pointing at, not a plan copied from a PDF.
- Clinician conversation — what was discussed with a licensed clinician; not a site prescription.
- Other non-shop hearsay — secondhand talk; lowest claim weight; still must not invent a plan.
Community Guidelines also require labeling the source. This lesson keeps shop-provided tips out of the Experience evidence path.
6. Uncertainty is not weakness
Required sentence patterns: “I am unsure which change mattered.” “I did not control for sleep.” “This may be expectation.” If you cannot write one, you do not have a finished observation yet.
7. Methods literacy — reading formal designs (not a DIY plan)
Formal single-patient trials and case reports use reporting checklists so readers can judge design, periods, outcomes, and transparency. CENT is a CONSORT extension for completed n-of-1 trials (Vohra et al., BMJ 2015; PMID 25976398). CARE is a consensus guideline for clinical case reports (Gagnier et al., 2013; PMID 24416692). Guyatt et al. (1986) described randomized trials in individual patients as designed comparisons, not victory stories (PMID 2936958).
Researchers sometimes plan multiple periods, predefined outcomes, blinding, and comparison windows (including washout windows between periods) so carryover and expectation are less mixed with the contrast of interest. That vocabulary helps you read a paper or a careful n-of-1 report. It is not an instruction to start, stop, time, or run a personal regimen. Peptide Student Field Notes on this site — the blog at `/blog/` — publishes short literacy notes. It is not a private trial binder and not a clinical trial registration.
8. Moderation preview
First posts are queued. Anecdote with labels → keep path. Plan language → return. Sourcing → remove. This is culture-setting, not a full moderation manual.
9. Close
Close: Lesson 5 takes up why “it worked for me” is data and not proof. This lesson has one job: label the observation before it hardens into a plan.
CTA after the lesson: Open the library · Continue Course 0 · Guidelines · Field Notes
Self-check
Ungraded. Reveal each answer after you attempt the question. No certificate.
1. Which field is intentionally absent?
Answer: Amount (and shop; and “would I recommend”).
2. True/False — Uncertainty can be skipped if you felt sure.
Answer: False. Uncertainty is required.
3. “Here is [amount]” as plan language belongs in Noticed.
Answer: False. That is plan language — return for edit.
4. Source label for “I am writing what I personally noticed”?
Answer: Firsthand.
5. Practical — Rewrite into fields (reveal model): “I used [compound-as-labeled] for [duration band]. Sleep felt better some nights. Training also got easier. Not sure which mattered. Someone said to buy from [source request] and use [amount] as a plan.”
Answer: Keep: compound-as-labeled, duration band, noticed (sleep), confounders (training), uncertainty. Reject/remove: source request and amount language. Source label: firsthand.
Log in or join to track your progress.Self-check is open to all. Progress tracking needs an account.