Implementation validation studies#

Each page here reports one study of a method that cleverly implements. A page exists only for a study registered in tests/studies/evidence/registry.py. The shared machinery in tests/studies/evidence/ computes every verdict, and tests/unit/test_method_evidence.py checks these pages against the committed results. Every table is generated from those results, so a stale number is a test failure and not a reading error.

Read the pages in this order.

page

what it gives you

Implementation validation grid

the eighty-five validation studies in one table, with the counts and the declared limits

How to read these studies

the three questions, the verdict rules, and the terms every study below applies

The red-cell ledger

every red verdict the studies publish, and the roadmap ask that owns each one

the eighty-six study pages

one row per committed test, with what it checked and the verdict its own endpoints produced

A validation study declares property cells or names a reference. A study that names a reference is comparator-backed, and its agreement block names the comparison kind of each row. The learned-rule boundary study declares neither, so it has a page and no grid row.

To register a new study, follow adding a method row.