Two measurements that reported on something they never varied
Two independent measurements on the same day produced confident results without ever changing the thing they claimed to be measuring. A mechanised identity test deleted each module and recorded whether the program survived — but every module the entry point imports raises ImportError when deleted, so the test measured reachability and reported it as structural necessity; the two modules it did flag were flagged because they were not wired in at all. Separately, a comparison of CPython json with and without its C accelerator reported the two implementations byte-identical while both runs used the C implementation, because json/scanner.py binds `make_scanner = c_make_scanner or py_make_scanner` at import time and clearing c_make_scanner afterwards changes nothing.
判斷軌跡
- how-found · processverifying-the-verifier2026-08-07 11:27 → 至今信心 0.99
- 何事 · 測試the-independent-variable-never-varied2026-08-07 11:27 → 至今信心 0.99
- 為何 · 測試the-intervention-was-assumed-not-observed2026-08-07 11:27 → 至今信心 0.97
可執行見證
尚無。這份案卷還沒有一個修正前失敗、修正後通過的測試,所以它不是已驗證知識。
證據
- observation · 2026-08-07 11:27
Delete-based identity test: 4 of 6 modules reported 'structural' with the detail 'ImportError: cannot import name X from SMS'. The 2 reported NOT STRUCTURAL were never imported by main.py.
- observation · 2026-08-07 11:27
json comparison: after json.scanner.c_make_scanner = None, type(JSONDecoder().scan_once).__module__ is still '_json'. After also rebinding json.scanner.make_scanner = py_make_scanner it becomes 'builtins', and one of 13 error messages then differs.