Report Image, Public Lab Page, and Merchant Transcription

Overview

When different public versions of the same report don’t perfectly match—such as a photographed report image, a laboratory’s public page, and a merchant’s product-page transcription—treat the lab’s dated public entry as the anchor, then compare the others against it for provenance, completeness, legibility, task identifiers, alteration risk, and how reliably each can be retrieved. Keep conclusions specific to the sample, method, matrix, and date, and remember that no single result demonstrates sterility, safety, efficacy, Canadian authorization, chain of custody, or batch-wide uniformity.

Start with provenance: who published what, and when

Provenance questions to answer:

If the answer to any of these is unclear, treat it as an unresolved point rather than assuming equivalence.

• Identify the lab’s own public entry. In this case, Jan Šik’s site presents a dated page for a specific MOTS-C analysis with a public report identifier and visible fields, including sample name, analyte, and test method elements . This page is the closest thing to an original public source for the lab’s findings and sets the baseline for what was published.
• Find any verification mechanism the lab provides. Janoshik offers a public verification page describing how readers can confirm whether a report entry matches what the lab has made public and understand the meaning of visible fields and signatures . Use this to check that the entry you are reading is part of the lab’s public set.
• Locate merchant copies or summaries. Growth Guys hosts a product page for MOTS-C 10 mg that includes a link-out and/or text summarizing a lab result and product details . This is secondary to the lab’s page and is useful for context, but it is not a lab publication. Note any differences between the merchant’s text and the lab’s own entry.
• Is there a direct link from the merchant page to the same lab page?
• Do names, dates, and key fields match across sources?
• Is any version missing the lab’s identifier or date?

Check completeness and legibility field by field

Compare the report image (if provided), the laboratory’s public page, and the merchant transcription for the presence and clarity of:

On Janoshik’s test page for MOTS-C, specific fields are publicly visible and include a public report identifier and named analyte entry . Ensure any report image reproduces those fields clearly. If an image crops fields, is blurred, or shows handwriting that cannot be read, mark those elements as unreadable rather than inferring content. If the merchant transcription summarises figures without reproducing the lab’s phrasing or omits the identifier or date, regard it as incomplete relative to the lab page .

When a field cannot be read in an image or is not present in a transcription, preserve uncertainty. Do not “fill in” from another version unless you can confirm the same page and date are being represented.

• Sample or product name
• Public report identifier shown on the lab page
• Date of analysis or publication
• Method information as presented by the lab
• Reported result fields (e.g., identification outcome, purity figure, or other stated values as displayed by the lab)
• Signature or lab statement as shown on the lab page

Use task identifiers to align versions, not to claim more than is shown

The lab’s public page displays a report identifier that readers can use to match across versions . Confirm that:

If an image or merchant page lacks the identifier, you cannot confidently assert it represents the same report, even if other details look similar. Record this as an unresolved point. Do not use an identifier to imply chain of custody, sterility, safety, efficacy, authorization, or batch-wide uniformity; the identifier only helps align the public documents. The lab’s verification page explains how public entries can be checked for authenticity on the lab site but does not convert a single result into broader guarantees .

• The identifier on the image (if visible) matches the identifier on the lab’s page.
• The merchant page cites the same identifier or links directly to the same lab entry .

Assess alteration risk and retrievability for each version

Retrievability tips:

• Laboratory public page: Lowest alteration risk when accessed directly from the lab’s website, because it is the lab’s own publication and can be revisited. If the page is public and dated with a visible identifier and fields, it is the primary reference for what the lab stated at that time . You can revisit it later or use the lab’s verification page to confirm that an entry remains consistent with the lab’s public set .
• Report image: Medium risk. Images can be cropped or edited. Check for missing edges, inconsistent fonts, or mismatched identifiers. If the image is hosted off the lab’s site without a verifiable link back, treat it as a reproduction with higher alteration risk. If the image matches the lab’s publicly visible fields, date, and identifier, it supports the same content; if not, uncertainty remains.
• Merchant transcription: Highest risk of drift. Transcriptions may compress language, round figures, or omit fields such as the identifier or date. If the merchant page links directly to the lab page and cites the same identifier and date, confidence improves, but the lab page still anchors the facts .
• Prefer a direct URL to the lab’s public entry and note the date you accessed it .
• Where the lab offers a public verification pathway, use it and record what it confirms in plain language (e.g., “the identifier appears on the lab’s public page on this date”) without extending the claim beyond visibility .
• Save screenshots of each public page with visible URLs and dates for your records, understanding that screenshots show what was visible, not what is universally true.

Keep conclusions tightly scoped and flag unresolved points

A practical sequence: 1) Open the lab’s MOTS-C entry and record the visible identifier, date, analyte, and result fields . 2) Read the lab’s verification page to understand what can be confirmed publicly and what cannot . 3) Compare any report image and the merchant transcription against the lab page, confirming identifier and date first, then fields and values . 4) Document any mismatches or unreadable fields as unresolved, without inferring missing content or broader claims.

• Scope your conclusions: State that any observation is specific to the sample, method, matrix, and date shown on the lab’s page . Avoid generalizing to other lots or future batches. Do not state or imply sterility, safety, efficacy, Canadian authorization, chain of custody, or batch-wide uniformity.
• Preserve uncertainty: If an image is unreadable in a section, say which field cannot be confirmed. If a merchant page lacks the lab identifier or date, note that the linkage to the lab entry remains unresolved . If the lab’s verification page describes general verification steps but does not display the specific entry you are checking, state exactly what is and is not established .
• Align before you compare values: Only compare numbers or qualitative results after confirming identifiers and dates match across versions. If they do not, stop at the mismatch and avoid cross-version value comparisons.