A research referee is only as trustworthy as its own discipline. Penrose is built so its checks can be
verified, not just asserted. This page summarizes how the system is calibrated and verified.
The relevant scripts are in scripts/ and run on a clean, keyless install.
- Placebo (specificity). Pure-noise signals applied to real returns yield zero strongest-state
certifications (
scripts/calibration_placebo.py, and the five-null batteryscripts/calibration_nulls.py). A referee that certifies noise is worthless; this one doesn't. - Injection (sensitivity). A planted signal is recovered: as injected signal strength rises, verdicts
move from
kill/underpoweredthroughwatchtoresearch-supportedat the expected threshold. - Tail-risk (widow-maker) control. The tail detector flags 100% of planted widow-maker payoffs
(small steady gains, rare large losses) as tail-asymmetric and false-flags 0% of benign symmetric
payoffs (
scripts/calibration_tail.py). The gate itself is opt-in; this validates the detector under it. - Process-conditional verdict. A single, byte-identical return series is certified or killed depending
only on the declared search lineage that produced it - the multiple-testing problem made concrete and
runnable (
scripts/worked_example_process_conditional.py). This is the cleanest demonstration of why Penrose is not a backtester, and it runs with no network, key, or data.
Every change is checked against the calibration suite and the real pipeline before it ships; controls that turn out to be no-ops are fixed, not left in place. Several real defects - a search that silently hid committed results, a "demonstration" whose claimed verdict did not survive the real pipeline - were caught and closed this way before release.
These controls establish that the referee discriminates signal from noise, accounts for search, and does
not certify the void. They do not establish that any surviving claim is profitable. A research-supported
verdict means "survived falsification," not "will make money" - and still requires human review. Penrose is
inspectable evaluation infrastructure, not an oracle, a publication authority, or a trading system.
Reproduce any of the above yourself: every script named here ships in the repository.