Current GROWTH10 verification

Current documented cart record — October 13, 2026 at 11:07 a.m. EDT

Code: GROWTH10 · Growth Guys · Discount observed: 10% · Method: Verified at checkout.

Documented pre-payment checkout record; no purchase was made.

View GROWTH10 current verification
← Verification resources

GROWTH10 editorial collection · Batch 8

When Growth Guys Sources Disagree, Keep the Claims Separate

Reader question: How should readers compare a cart record, merchant page, lab link, social post, and search result?

Short answer: treat each document as a dated claim about a single event, record its exact wording and timestamp, match that wording to a concrete piece of evidence, and record any unresolved differences rather than averaging them — then use a conflict protocol that preserves those differences and shows what remains unproven. Do this for every cart record, merchant page, lab link, social post, or search-result snapshot you compare [1] [3].

Why this matters: different sources can describe the same transaction or product in incompatible terms (for example, a cart record that lists a SKU, a merchant page that promises eligibility, a lab-results page that lists a test, and a social post that discusses availability). Treating them as separate claims prevents conflating a historical note with present eligibility or turning an incomplete attempt into proof of rejection.

How to read evidence: a source-by-question matrix Below is a practical matrix you can apply to a specific event (purchase, listing, test publication, or social post). Use it for each source and each question you need answered. Keep every conclusion tied to the identified event and timestamp.

Essential columns for the matrix:

  • Source identifier: name and exact URL used (record the full link and its snapshot time).
  • Document timestamp: date/time on the page or the time you archived/saw it.
  • Exact claim text: quote the precise sentence or table cell you are evaluating.
  • Question being asked: e.g., “Did the merchant accept payment?”, “Does the lab report match this batch number?”, “Does the listing promise eligibility for program X?”
  • Matching evidence in the source: point to the field, image, or linked file that supports the quoted text (give element location: cart line, header, PDF link).
  • Conflicts/unresolved differences: note any direct contradictions with other sources and list what remains unknown.

Example rows (conceptual — fill with the event’s own details)

  • Source identifier: Cart snapshot (save URL and screenshot).
  • Document timestamp: visible order time or archive time.
  • Exact claim text: “Item added to cart: SKU 1234 — 2 units.”
  • Question asked: “Was an item selected and quantity indicated?”
  • Matching evidence: cart line item, quantity selector.
  • Conflicts/unresolved: merchant page shows SKU 1234 back-ordered as of same date — unresolved whether checkout completed.
  • Source identifier: Merchant product page [2].
  • Document timestamp: page footer or archive timestamp.
  • Exact claim text: “Eligible for program X.”
  • Question asked: “Does the merchant promise eligibility?”
  • Matching evidence: page section with eligibility text.
  • Conflicts/unresolved: lab-results page [3] lists tests but does not state program eligibility — unresolved whether the page’s claim was accurate for the batch sold.
  • Source identifier: Lab-results archive [3].
  • Document timestamp: test publication date on the lab report.
  • Exact claim text: table row showing analyte and result; batch or sample ID if present.
  • Question asked: “Does this lab report correspond to the shipped batch or a different sample?”
  • Matching evidence: batch/sample ID, chain-of-custody fields (if present).
  • Conflicts/unresolved: cart and merchant listings lack batch ID — unresolved link between lab report and purchased unit.
  • Source identifier: Social post or verification desk entry [4] [1].
  • Document timestamp: post time or verification timestamp.
  • Exact claim text: e.g., “Available now at Location X.”
  • Question asked: “Does this assert availability at the same time as the cart/merchant claim?”
  • Matching evidence: content of the post, any embedded images/screenshots.
  • Conflicts/unresolved: search result snapshot shows a different availability status — unresolved which reflects reality at that timestamp.

Conflict protocol: step-by-step

  1. Record provenance first. For every source, capture the full URL you used, the visible on-page timestamp if present, and the time you archived or screenshot it. Use those timestamps as the event’s anchor. If the source itself does not show a date, record when you observed it and label that record timestamp clearly.
  1. Quote the claim verbatim. Do not paraphrase when establishing what the source asserts. Exact wording matters because small differences (will ship vs. in stock vs. eligible) change meaning.
  1. Map claim to evidence fields. Point to the concrete field, table cell, PDF page number, or image element that supports the quoted claim. If a document links to another file (for example, a lab report PDF), treat the linked file as a separate source and apply the same steps.
  1. Identify direct contradictions. Compare the exact quoted claims across sources. If one source asserts “in stock” and another asserts “back-ordered,” mark these as incompatible. Do not average them into “partially in stock.” Maintain separate entries: Source A claims X at time tA; Source B claims not-X at time tB.
  1. Seek linking evidence before inferring relationships. To connect a lab report to a purchased unit you need a batch or sample identifier that appears in both the lab report and the merchant or cart record. Absent that identifier, record the lab report as evidence of testing of a named sample at a date — but not as proof that the tested sample was the item sold.
  1. Resolve what can be resolved; flag what cannot. Some differences can be reconciled by timestamps (e.g., merchant updated stock status after a purchase time). Others remain unresolved because of missing identifiers or unclear chain of custody. List both resolved alignments and unresolved gaps explicitly.
  1. Preserve historical limits. For every conclusion, state the exact event and timestamp it applies to, and add this required caveat: a historical record neither proves present eligibility nor turns an incomplete attempt into evidence of rejection. The fact that a lab report existed on date T does not prove that any later shipment was tested; a cart record showing checkout on date T does not prove acceptance or delivery unless a distinct acceptance/delivery record with time is present.

When sources lack necessary linking details If a merchant page and a lab-results page each exist but neither includes a shared batch or sample ID, treat them as independent statements about different events. You may note temporal proximity (e.g., both dated within the same week) but must mark the relationship as unproven. Do not combine them into a single claim about the same unit.

Usefulness, not transaction advice This approach is aimed at giving readers a clear, evidence-led method to compare records and flag contradictions. It is not a checklist for asserting any legal or regulatory outcome; it helps show what each source actually claims and what remains unresolved. Apply it to cart records, merchant pages, lab links, social posts, and search-result snapshots alike, and keep every conclusion tied to the identified event and timestamp so the evidence trail stays auditable and specific [1] [3].

References

  1. GROWTH10 Verification Desk
  2. Growth Guys Canada homepage
  3. Growth Guys Canada lab-results archive
  4. GROWTH10 Verification Desk

Current evidence

Read the current GROWTH10 verification record

Current cart evidence and historical records are maintained separately from this editorial guide.

Open the current record →
GROWTH10 Verification Desk
GROWTH10
Shop