How we test
The receipts behind the word "tested."
The rule: nothing carries a tested badge unless it was cooked in this kitchen, measured with a scale and a probe thermometer, and logged with a date. Not "looks right." Not "the source is reputable." Cooked, here.
What a test involves
- Doneness by temperature, not vibes. Every protein gets a pull temp in the steps — and when the internet's version is wrong, we say so (chicken thighs want 175–185°F, not the 165°F every blog copies; the collagen doesn't care about the safety chart).
- The math gets checked. The viral protein ice cream claimed 25g protein per serving; one scoop split two ways is 13g. Ours uses two scoops because arithmetic is not a garnish.
- Failure modes are documented. Every tested recipe carries a "When it goes wrong" section — because the difference between a recipe that reads well and one that works is what happens when your pan is too hot.
- Changes are logged. Each tested recipe carries a dated note of what was verified or changed. When we fix something, the fix is public.
Where the recipes come from — honestly
This is a curated collection, not 164 acts of invention. Many recipes are adapted from sources we respect — Serious Eats, America's Test Kitchen, King Arthur, Marcella Hazan — and every one says so, on the page, by name. Adaptation is how cooking has always worked; pretending otherwise is how recipe blogs work.
The back-catalog is being retested to the rcpbx spec one dinner at a time. Until a recipe has been cooked here, it wears retest scheduled instead of a tested badge. We'd rather show you an honest queue than a dishonest trophy case.
The Radar
Every week we cook the internet's loudest viral recipe and file a verdict: WORTH IT, OVERHYPED, or SKIP. Verdicts are dated, permanent, and occasionally unflattering — the failures get buried in the SKIP file with a cause of death. The trend gets 15 seconds of fame; the verdict is forever.