Editorial standards
Last updated
These are not aspirations. Each rule below is enforced by the publishing system itself, and a page that breaks one is rejected before it can go live.
Every number traces to a stored, dated observation
Nothing is published from memory or from a model's guess. Each figure on a page is read back out of an append-only history row, and the page states the date that row was captured. If the capture is old, the date on the page says so.
Generated pages are validated in code after generation
After a page is generated, it is checked against the source data it was generated from. Any number appearing in the page that is not present in that source data causes the page to be rejected rather than published. A rejected page produces no public URL at all.
Nothing material changed means nothing gets published
Publication requires an identified material event — a movement in the underlying data large enough to clear a configured threshold. Data values on their own never authorise publishing. Where a period genuinely contained no material change, we say so as a finding, with the real tracked count and date range, instead of hiding the section or padding it with filler.
Income claims are blocked automatically
Income claims, earnings promises, fabricated testimonials and invented user counts are blocked by an automated check that runs over generated copy before publication. This is a hard gate, not an editorial preference.
Provenance is classified on every observation
Each stored observation carries a provenance class: reported (published by the source), observed (seen directly by our collectors), first-party tested (measured by us in a hands-on test), derived (computed from other stored values), or estimated. Estimated values are excluded from buyer-facing scores.
Commission economics never touch the buyer-facing score
The buyer-facing Product Score contains no commission rate, payout, EPC or earnings data at any weight. The affiliate-facing Opportunity Score does consider those things and never appears on a buyer-facing page. The separation is enforced by the database schema and the rendering layer, not by policy alone. The dependency runs one way only: Product Score may feed into Opportunity Score, never the reverse. Full formulas: /methodology/product-score and /methodology/opportunity-score.
Corrections
If you find an error, email jack@jackdoesdigital.com with the page and what is wrong. Verified errors are corrected on the page itself, and the page's updated date reflects the correction. We do not quietly delete pages to make an error disappear.