What we never say
The last lesson is the discipline itself: what these numbers refuse to claim, and why that restraint is the product.
The answer first
Everything on this site describes resolved past behavior on a public record. Nothing on it is investment advice, a forecast, a rating of a person, or a promise about the future. Those are not legal boilerplate lines; they are the boundary of what the evidence supports, and the site is engineered so the boundary travels with every number.
The intuition, with one worked example
Here is the same finding written two ways. The hype version: "Our score predicts which traders win next." The receipt version: we committed in advance to a test of exactly that claim, with a +0.30 bar filed before any analysis ran. The frozen-coefficient leg came in at +0.111 (95% CI 0.05 to 0.18) and the refit leg at -0.082, below zero. Both legs missed the bar. So the public claim is the second version: the composite ranks past behavior across wallets and did not clear its own forward test, which is published in full on the negative-results page and stays published. A site that only ever reports wins is indistinguishable from a site that buries losses. Publishing the miss is what makes the other numbers worth reading.
The actual method
The discipline, as enforceable rules:
- Not advice, not a forecast. Every API verdict ships a fixed line that cannot be disabled: "Diagnostics on a public on-chain record, not investment advice, not a forecast." The badge carries its caveat in every view.
- In-sample says in-sample. A skill read is a property of the resolved past record. The skilled state's own definition ends with "retrospective and in-sample."
- Forward claims wait for forward tests. The persistence questions are covered by tests filed in advance with an independent registry; their verdicts compute mechanically from time and outcomes, and they are pending while the windows mature. A null verdict would be published as a valid outcome.
- No estimate without its interval. Enforced in the schema and the export code, not by editorial habit (lesson 3).
- A word gate on every build. An automated check scans public copy and blocks a list of certainty words unless the receipt exists. The failed-test archive stays linked in the site footer.
Where you see this on the site
The footer of every page links Failed Tests next to the research itself. Method receipts and the hash-chained evidence log live at /research/preregistrations and /evidence, and /independence documents that Convexly takes no venue revenue, so no verdict here is paid for by the thing it measures.
What this does NOT mean
Restraint does not mean nothing works. It means the numbers you do see survived the checks in these twelve lessons: a price-netted measure, an interval, a structural screen, a multiplicity correction, and a placebo baseline, with the misses published alongside the hits. That is the whole idea of the site in one sentence: the confidence you can place in a number should come from the process that produced it, not from the volume at which it is stated.
Convexly publishes new methodology research roughly every 6-8 weeks plus the /learn series on a rolling cadence. Get the next paper in your inbox when it ships:
Frequently asked
Why does every Convexly read carry a disclaimer?
What is the difference between in-sample and forward?
Has Convexly ever published a test that failed?
Related surfaces
- /research/negative-results: every failed test, published and dated
- /independence: why no verdict here is paid for by a venue
Related reading
LearnBrier score
LearnCalibration
LearnCohort audit