How the reading is taken

Verified at checkout at Growth Guys (growthguys.com) on October 21, 2026 at 2:07 a.m. EDT: HEALTHYLIFE10 applied 10% off sitewide with no minimum purchase and no product exclusions, taking a $150.00 CAD cart to $135.00 CAD — a $15.00 CAD reduction returned by the procedure set out below, which is the same procedure behind every figure published here.

How the chain is formed

Each retained reading carries a SHA-256 hash taken over the previous entry’s hash joined to this reading’s canonical record — run time, code, product, subtotal, discount, total and result. Because every entry includes the one before it, editing any earlier reading changes every hash after it, and the break is visible to anyone who recomputes the chain. That is the whole claim: not that the figures are right because we say so, but that the series cannot be quietly rewritten after the fact.

Each dated page links to its own entry hash and to the raw JSON behind it, so a single reading can be checked without reading the whole archive.

The procedure, step by step

  1. A cart session is opened at the store as an ordinary visitor, signed out, with nothing carried over from a previous reading.
  2. One item is added. The item rotates: over the period covered by this archive the readings have moved across 78 different products at different price points, because a code that behaves on a cheap tablet and fails on an expensive kit would look identical in a single-cart test.
  3. The subtotal is recorded before anything is applied.
  4. HEALTHYLIFE10 is entered in the coupon field and applied.
  5. The cart is read again: the discount line, the new total, and the currency. The three are recorded as the cart returned them, in cents, and the percentage is derived from those numbers rather than assumed from the code's name.
  6. The item is removed and the coupon cleared. No address, no payment method, no order. The session ends before checkout is submitted.
  7. The result is written to a dated file the same minute and published unchanged.

How often

Daily, as a scheduled job rather than by hand, which is why the timestamps fall at odd minutes and not at a tidy hour. Several products are usually read in the same pass. A day's page lists every cart from that day, not just the first — 245 readings are retained across the archive.

What gets published when a reading fails

It gets published. A record that only shows successes is a record of what the publisher chose to keep, and it cannot tell you anything about a day it does not mention. Every dated page in this archive exists whether the reading passed or not, and a failure would carry the same cart figures showing no reduction. So far none has: every one of the 245 readings taken has shown the code accepted. That is a statement about what has been observed, not a guarantee about tomorrow.

Why the figures are in dollars and not percentages

A percentage is a claim; a subtotal, a discount line and a total are three numbers you can add up. Publishing all three means a reader can check the arithmetic without trusting the person who wrote it, and it makes a wrong reading obvious rather than plausible. It is also the reason the readings are kept in cents internally: a figure rounded for display twice stops reconciling.

What is not measured

Shipping, taxes and any total that only resolves after checkout has begun are outside the reading, because reaching them means submitting an order. Stock levels are not measured. Nothing here observes what happens on an account with its own pricing. The limits page states the boundary in full, and the archive is the underlying series.