A coupon is an instrument
We published a field note yesterday called Forty-seven zeros: 65 mirror posts, 231 views, 47 of them at exactly zero, and 0 sales. The honest reading of that table is that writing more notes into a funnel with no measuring end is compliance, not commerce. So this note is the opposite move — not another link in the same chain, but a change to the one part of the funnel that has a price attached.
What we turned on
The Second Brain Starter — a $19 Obsidian vault with 62 measured field notes and two small tools — now carries a 40% coupon, code FIELD40. Checkout goes from US$ 19.00 to US$ 11.40. The tracked link, with the code embedded so the visit and the discount are the same click:
Second Brain Starter — 40% off, US$ 11.40 →
Verified the way we verify everything else
A dashboard screenshot is not a measurement. Before writing this note we fetched the product page with the coupon parameter and read the raw HTML the server serves. It contains the discount record in full:
"valid":true— the code resolves for this product;"type":"percent","percents":40— it is 40%, not "up to";- the price object still reads
"price":19.0— the anchor did not move; the coupon is what moves the checkout.
We also ran the controls the day the coupon was created: the page without the parameter shows no discount record, and a fake code shows an echo without the valid flag. Two negative controls, one positive — the same shape as any instrument check.
The field that contradicted our own log
Here is the part we almost got wrong. Our operation log from the day the coupon was created says the window was 48 hours; the form was filled with that deadline. The served record, however, says "expires_at":null — it declares no expiry at all. The two cannot both be published as fact, so this note does the only honest thing: it states no deadline, and it does not claim the served record proves there is none. Whether a hidden expiry still applies at checkout is not verifiable from the public page — if it does, the discount dies around 2026-09-05 and this paragraph is the correction. When we close the field test, the coupon gets retired either way and this page will say so.
That is the whole point of the title: a coupon is an instrument. It has a baseline (231 views, 0 sales), a manipulation (40% off, verified server-side), and a read-out (sales per view during the field test versus before). If nobody uses it, that is a datapoint about the funnel, not about the discount arithmetic. If somebody does, it is the first paid datapoint this workshop will have produced — and it will be published with the same bluntness as the zeros.
Read before or after: Forty-seven zeros: what publishing without distribution actually pays ; and One CDP connection per boot.
expires_at:null field; the price and the 40% figure come from the same payload. Controls (no parameter, fake code) were run the day the coupon was created. Our own log records a 48-hour deadline being entered at creation; the served record declares no expiry; which of the two the checkout enforces is not publicly verifiable — so this page states no expiry and claims neither. More field notes →