复核不是重扫一遍:审计工具升级后该查的四种东西

Written by

in

Language

Evidence level: C

方法学记录 · 池④ #67 · 2026-10-24

上一轮(第 17 轮)我们修好了审计工具的两个缺陷——R16(判定”谁在主张”从文件名改为文字形态)和 R17(排除规则必须对称施加)。修完工具只是第一步。真正要回答的问题是:修好了,然后呢? 这一轮做的就是这件事——不是再扫一遍就收工,而是按四个角度验证”修复是否真的有效、有没有留下新的坑”。

一、同一把尺子量两次:修复的稳定性

判断一个审计工具修复有没有效,最便宜的方法是隔一轮什么都不改,用同一把尺子再量一次。

第 17 轮修复后,R5X(跨文件自相矛盾检查)报出 6 条违反。本轮在不改任何正文的情况下重跑,数字是:

  • R5X 违反:6 条(一条不多一条不少)
  • 跨文件配对:14 组(不变)
  • 因转述/审计文排除的点:7 个(不变)
  • R5(同文件检查):1 条(不变)
  • selftest:92/92(不变)

数字完全一样,这本身就是信息。上一轮第 17 轮我们刚抓到过”什么都没改、隔一轮重跑,违反数从 6 涨到 16″——那是工具在指控自己上一轮写的文章。本轮数字纹丝不动,说明第 10 类失败模式(自指污染)没有复发,R16 的修复是真修好了,不是碰巧。

二、换一个方向再判:6 条违反是不是同一个根

数字稳定还不够。还得问:这 6 条违反,到底是一个问题还是六个问题?

本轮逐条核对 R5X 报出的 6 条:4 条的一侧是同一文件同一张表(skin-depth-basement 的 §3 衰减表 L81/L82/L85),第 6 条的另一端也是它。这和第 17 轮的判断完全一致——6 条不是 6 个笔误,是 1 处根错派生的 6 个症状。

独立手算复现(f=7.83 Hz,μ0=4π×10⁻⁷):

材料(按文件自述 σ) δ @7.83 Hz 100 m 的 A 1 km 的 A
花岗岩 σ=1e-4 17.986 km 0.048 dB 0.48 dB
花岗岩 σ=1e-5 56.88 km 0.015 dB 0.15 dB
玄武岩(湿)σ=1e-2 1.799 km 0.48 dB 4.84 dB

对照文件 §2 表声明:花岗岩 δ @7.83 Hz 写的是「32 m」。真值 17.986 km → 差 562×。同一份文件 §3 表把 100 m 花岗岩写成「27 dB」,真值 0.048 dB,也差 562×。两个数字差同一个倍数,不是巧合——它们共用同一个错的 δ。

为什么这个错值得认真对待:这份文件的立论是「山体对 ELF 几乎透明、靠山屏蔽不成立」。按错值(100 m 27 dB),山体像强屏蔽体;按真值(0.048 dB),几乎不挡。这个错把正确的结论写得在它自己的文件里显得不成立。 更实际的是:δ 低估 562× ⇒ A 高估 562× ⇒ 撑起”普通花岗岩山值得测”,而按 #22 的分档,普通花岗岩是 C 档(最不该优先测)——会把测量预算投到错误样本上。

三、查工具自己:版本自述与实况一致吗

第三件事是查工具自己有没有说谎。本轮发现一个很隐蔽的小 bug:

扫描报告头部自述 delta-table-scan.py v1.5,但文件的字节数和 selftest 数量都指向 v1.6。查源码定位:报告标题行的版本号是硬编码的,v1.6 升级时漏改了(delta-table-scan.py L1243)。

这看起来只是个展示问题,但它的性质值得警惕:工具自述失真。如果下游有人把”报告标题 v1.5″当成版本依据——尤其当磁盘上同时躺着 v1.5 的备份(bak-20261023-v15)时——就会误判你实际用的是哪一版工具。本轮已把标题改为从 docstring 动态提取最大版本号,改后 selftest 仍 92/92、全库扫描数字与改前完全一致(判定逻辑零改动)。

方法学增量:审计工具的升级清单里,应该有一条”版本自述同步”检查——升级判定逻辑是功能,升级自述是卫生。两者都要做。

四、查修复的代价:形态屏蔽有没有误伤

第四件事最容易被跳过:新规则有没有误伤不该伤的东西。

R16 把”引号/代码块内的数字”一律不算主张。它会不会把表格里确实在主张的数字也屏蔽掉?本轮核查:

  • 全库表格内引号数字 118 处,绝大多数是 DOI 反引号引用(10.xxxx)与审计文里的对照说明,不构成裸主张,屏蔽正确。
  • 未发现”表格里写 「27 dB」 且确实在主张”的案例。
  • 上轮自指边界示例(pool4-selftest-contamination-single-root-error.md L103)已规避——只描述形状、不给具体值,实测无误报。

已知盲区(非本轮新增):把数字写进引号但确实在主张的文件,R16 会漏(实测 0 例,理论盲区);R14 排除名单仍按文件名正则(#66 正向化待做)。两者都不阻塞本轮结论。

证据与局限

  • 证据等级 C(E3 结构类比):全部为解析复算 + 库内文本核算,无任何实测。A ≈ 8.7d/δ 与 δ=√(2/(ωμσ)) 假设均匀半空间、无位移电流、μr/σ 为常数;真实山体分层各向异性且 σ 随频率弥散(Kariya & Shankland 1983 10.1190/1.1441407 / Laštovičková & Bochníček 1992 10.1007/BF01613900 / Revil 2013 10.1029/2012WR012700 / Mehran & Arulanandan 1977 10.1346/CCMN.1977.0250107,4 DOI Crossref 回查通过,均非 PubMed → 无 PMID)。
  • 局限:R5X 判”违反”仅指两文件数字不满足 A ∝ d,不指真实地下 A 为另一值;§1 自述 σ 区间本身未审计;分母极小(35 点 / 14 组配对),不得外推”全库矛盾率”;只覆盖等式断言(R13);屏蔽规则是形态启发式,把数字写进引号但确实在主张的文件会被漏(已知盲区,实测 0 例)。

下一步(留给 JOE 决策)

  1. #68(P1,须 JOE 批):改 skin-depth-basement §2 表花岗岩 δ 一格(32 m → 17.99 km,5 频点连带)——唯一一项”改一格消 6 条违反”的动作,且直接决定 #22/#23/#25 的采样点名。建议与 D1′ 合并提请(同源:都是”σ/δ 低估导致误以为普通花岗岩值得测”)。
  2. #65(P2,可自主):12 条区间断言逐条判”该不该写成区间”。
  3. #59(P2,可自主):F2 余 4 + F3 余 6 逐格复算。

免责说明:本文属传统知识与科学文献的整理、对照与研究设计讨论,仅供理解与参考,不构成医疗建议,不能替代专业诊断与治疗。文中涉及的效应量、频率区间与暴露结论多为研究报告层面的推断,个体情况差异很大;如有身体不适或健康疑虑,请就医并由专业医师判断。

pool4-r16-r17-full-rescan-review

Evidence level: C

Methodological record · Pool④ #67 · 2026-10-24

In the previous round (Round 17), we fixed two defects in the audit tool—R16 (changing “who is making a claim” from filename to textual form) and R17 (ensuring exclusion rules apply symmetrically). Fixing the tool is only the first step. The real question to answer is: Now that it’s fixed, what next? This round addresses exactly that—not simply re-running the scan and calling it done, but verifying from four angles whether “the fix is truly effective and no new pitfalls have been left behind.”

I. Measuring twice with the same ruler: stability of the fix

The cheapest way to judge whether an audit tool fix is effective is to run it again without any changes in the next round, using the same ruler.

After Round 17’s fix, R5X (cross-file self-contradiction check) reported 6 violations. Running the same scan again without modifying any text, the numbers are:

  • R5X violations: 6 (one more, one less—exactly the same)
  • Cross-file pairs: 14 (unchanged)
  • Points excluded due to paraphrase/audit text: 7 (unchanged)
  • R5 (same-file check): 1 (unchanged)
  • selftest: 92/92 (unchanged)

The numbers are exactly the same, which itself is information. In Round 17, we just caught “nothing changed, re-run next round, violation count rose from 6 to 16″—that was the tool accusing itself of its own previous round’s articles. This round’s numbers remain unchanged, indicating that failure mode #10 (self-reference contamination) has not recurred, and R16’s fix is truly fixed, not coincidental.

II. Checking from another direction: are the 6 violations all rooted in one problem

Stable numbers aren’t enough. We must also ask: are these 6 violations all one problem or six separate ones?

This round, we checked each of the 6 violations reported by R5X individually: 4 violations have one side in the same file and same table (skin-depth-basement §3 attenuation table L81/L82/L85), and the other end of violation #6 is also in it. This matches exactly the judgment from Round 17—these 6 violations are not 6 typos, but 6 symptoms stemming from 1 root error.

Independent manual recalculation (f=7.83 Hz, μ0=4π×10⁻⁷):

Material (as stated in file σ) δ @7.83 Hz A at 100 m A at 1 km
Granite σ=1e-4 17.986 km 0.048 dB 0.48 dB
Granite σ=1e-5 56.88 km 0.015 dB 0.15 dB
Basalt (wet) σ=1e-2 1.799 km 0.48 dB 4.84 dB

Comparing with the file’s §2 table declaration: granite δ @7.83 Hz is stated as “32 m“. True value 17.986 km → off by 562×. In the same file §3 table, 100 m granite is stated as “27 dB“, true value 0.048 dB, also off by 562×. Both numbers differ by the same factor, not coincidence—they share the same wrong δ.

Why this error matters: This file’s thesis is “mountains are nearly transparent to ELF, shielding by mountains doesn’t hold.” Based on the wrong value (100 m, 27 dB), mountains act like strong shields; based on the true value (0.048 dB), they barely block anything. This error makes the correct conclusion appear invalid within its own file. More practically: δ underestimated by 562× ⇒ A overestimated by 562× ⇒ supporting “ordinary granite mountains worth measuring,” while according to #22’s classification, ordinary granite is Category C (least priority)—this would misallocate measurement budget to wrong samples.

III. Checking the tool itself: does the version statement match reality?

The third thing to check is whether the tool itself is lying. This round found a subtle bug:

The scan report header states delta-table-scan.py v1.5, but the file’s byte count and selftest numbers both point to v1.6. Tracing the source code: the version number in the report title line is hard-coded, and v1.6 upgrade missed updating it (delta-table-scan.py L1243).

This looks like just a display issue, but its nature is worth caution: tool self-statement is distorted. If downstream users take “report title v1.5” as the version basis—especially when both v1.5 backup (bak-20261023-v15) and v1.6 files coexist on disk—they may misjudge which version of the tool is actually in use. This round has changed the title to dynamically extract the maximum version from docstring; after change, selftest remains 92/92, full-library scan numbers match before modification exactly (judgment logic unchanged).

Methodological increment: In the audit tool upgrade checklist, there should be an item “version statement synchronization”—upgrade judgment logic is functionality, upgrade statement is hygiene. Both must be done.

IV. Checking the cost of the fix: did new rules wrongly shield things they shouldn’t?

The fourth thing is most easily skipped: did the new rules wrongly shield things they shouldn’t have.

R16 excludes “numbers inside quotes/code blocks” from being claims. Could it also shield numbers in tables that are indeed making claims? This round checked:

  • 118 instances of quoted numbers in tables across the whole library, most are DOI backtick references (10.xxxx) and audit text cross-references, not bare claims, so shielding is correct.
  • No cases found where “table says 「27 dB」 and it is indeed making a claim.”
  • Previous self-reference boundary example (pool4-selftest-contamination-single-root-error.md L103) has been avoided—only describing shape, not giving specific values, tested with no false alarms.

Known blind spots (not added this round): files that write numbers into quotes but are indeed making claims, R16 will miss them (tested 0 cases, theoretical blind spot); R14 exclusion list still uses filename regex (#66 forwardization pending). Neither blocks this round’s conclusion.

Evidence and limitations

  • Evidence level C (E3 structural analogy): All are parsed recalculation + library text calculation, no actual measurement. A ≈ 8.7d/δ and δ=√(2/(ωμσ)) assume uniform half-space, no displacement current, μr/σ constant; real mountain layers are anisotropic and σ disperses with frequency (Kariya & Shankland 1983 10.1190/1.1441407 / Laštovičková & Bochníček 1992 10.1007/BF01613900 / Revil 2013 10.1029/2012WR012700 / Mehran & Arulanandan 1977 10.1346/CCMN.1977.0250107, 4 DOI Crossref lookup passed, none are PubMed → no PMID).
  • Limitations: R5X judging “violation” only means two files’ numbers don’t satisfy A ∝ d, not that true underground A is another value; §1 stated σ interval itself was not audited; denominator extremely small (35 points / 14 pairs), cannot extrapolate “whole-library contradiction rate“; only covers equation assertions (R13); shielding rule is morphological heuristic, files that write numbers into quotes but are indeed making claims will be missed (known blind spot, tested 0 cases).

Next steps (for JOE decision)

  1. #68 (P1, requires JOE approval): Fix skin-depth-basement §2 table granite δ by one cell (32 m → 17.99 km, 5 frequency points linked)—the only action of “fixing one cell to eliminate 6 violations”, and directly determines #22/#23/#25 sampling names. Suggested to merge with D1′ submission (same origin: both “σ/δ underestimated leads to thinking ordinary granite worth measuring”).
  2. #65 (P2, can be done independently): Judge each of 12 interval assertions “should it be written as an interval.”
  3. #59 (P2, can be done independently): Recalculate F2 remainder 4 + F3 remainder 6 cell by cell.

Disclaimer: This article compiles traditional knowledge and scientific literature for comparison and research-design discussion only. It is not medical advice and cannot replace professional diagnosis or treatment. Effect sizes, frequency ranges and exposure conclusions cited here are largely inferences at the research-report level, and individual circumstances vary widely. If you have any discomfort or health concerns, please consult a physician.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *