Evidence level: C
一句话结论:本库的跨文件一致性审计工具,判断”哪个文件在主张一个数值、哪个文件只是在引用”时,原来靠文件名正则猜(文件名含 audit/governance/backlog 才算”引用方”)。这个办法有一个结构性后门:审计文、实验设计、台账只要文件名不像审计文,就被当成”主张方”——于是工具会指控”忠实记录错误”的台账和”忠实引用正本”的实验设计,而不是指控真正写错的正本。这一轮把它改成按目录角色定:
03-sites/是正本(网站材料落点),08-ops/是内部工作区(实验设计/治理卡/台账,一律引用方)。改完,跨文件假阳性少 1 条,剩下的 5 条违反全部指向两个已知伤口。
一、这个工具在干什么
池④ 有一张”趋肤深度—衰减”对照表(δ 表),被十几个下游课题当共同基准。为了防这张表继续带错数值传播,我们写了一个跨文件扫描器(delta-table-scan.py),它做三件事:
- R1/R2/R3:把任意 md 里的 δ / A(dB) 数值断言抽出来,用”该断言自己声明的 σ/μr”独立复算,判定是否自洽。
- R5(同文件内):同一个文件里,同一材料同一频点下若出现两组”厚度—衰减”,两者之比必须相等(
A ∝ d,零参数)。 - R5X(跨文件):两个文件对同一材料同一频点给出互不相容的数字 → 报违反。
R5X 是 R5 的跨文件版,也是它第一次真正抓到本库的主体缺陷形态——双语镜像 + 审计文互引的库里,同一个数字经常同时出现在正本、审计文、backlog 三处。
二、问题:按文件名猜”谁在主张”会冤枉谁
R5X 一开始遇到 32 对假阳性,收敛到 6 对靠的是两条规则,其中一条叫 R14「引用的不是主张」:审计文/台账里并排写的是”原文值 vs 复算值”,两数本就该不同;把它们当主张方,等于把”有人在引用错值”读成”这个文件也错了”。
但 R14 当时是按文件名正则实现的:
文件名含 audit / governance / backlog / report / registry / check / integrity / decision / queue / ledger → 不作主张方
这个办法漏了两类文件,而且漏的都是”本应被信任”的文件:
- 审计文文件名不像审计文(第 17 轮撞上):
pool4-cross-file-a-proportionality-contradiction.md名字里没有 audit/backlog,但它确实是审计文——它把”散文 0.27 dB / 表 27 dB”这一对已知矛盾并排写进正文当例子,被工具当成主张方,一次报出 16 条假阳性。 - 实验设计、治理卡、台账(本轮撞上):
08-ops/experiments/pool4-mountain-elf-typical-granite-transparent.md是配套实验设计,它在引用正本的 0.27 dB,名字里也没有任何审计词 → 被当成主张方,与正本互比,凭空多出 1 条违反。
这两类文件的共同点:它们不是网站正本,是内部工作区。文件名正则永远猜不全”谁是工作区”——靠猜,就会有一个漏网之鱼,而且漏的都是最该被保护的”忠实记录者”。台账越忠实记录错误,越会被自己的工具判成有错——这是一个鼓励”少记录”的反向激励,必须用结构消灭。
三、修法:目录角色说了算,文件名不再参与
把”谁在主张”从”按文件名猜”改成”按目录角色定”:
def _is_quote_doc(rel):
# 真实路径不在 03-sites/ 下(即 08-ops/ 内部目录)→ 内部工作区,一律不作主张方
if os.sep in rel and not rel.replace(os.sep, "/").startswith("03-sites/"):
return True
return bool(QUOTE_DOC.search(os.path.basename(rel))) # 裸文件名(夹具)仍按正则
语义很直白:
03-sites/= 网站材料正本落点 → 主张方(该信它说的数,也该被审计)。08-ops/(pools / experiments / decisions / 台账) = 内部工作区 → 引用方(它写的数是在引用正本,不是新主张,不参与互比)。- 裸文件名(selftest 夹具、临时文件)→ 退回文件名正则(保留”审计文不算主张方”的测试语义)。
为什么不是”看 frontmatter 有没有 pool 字段”:08-ops/experiments/ 下所有实验设计都没有 pool frontmatter(本轮已核),两种口径结果一致;但目录角色不依赖每个文件的 frontmatter 是否写全,也就不怕”某个实验设计以后补了 pool 字段”而悄悄变成主张方。目录是结构事实,frontmatter 是书写习惯——结构事实更稳。
四、实测:违反 6→5,剩下的全是正本互比
同一工具、同一扫描根(--root . 全库)重跑:
| 指标 | v1.6(上一轮) | v1.7(本轮) | 变化 |
|---|---|---|---|
| 命中文件 / 断言总数 | 52 / 553 | 52 / 553 | 不变 |
| MISMATCH(OK/param/unit) | 297(208/240/33) | 297(208/240/33) | 不变 |
| RANGE-unjudged | 48 | 48 | 不变 |
| 表格覆盖率 | 63/83 = 75.9% | 63/83 = 75.9% | 不变 |
| R5 违反 | 1 | 1 | 不变 |
| R5X 违反 | 6 | 5 | −1 |
| R5X 配对 | 14 | 10 | −4 |
| R5X 排除点 | 7 | 8 | +1 |
| selftest | 92/92 | 92/92 | 不变 |
- 消除的 1 条:
granite @ 7.83 Hz,A 端是实验设计08-ops/experiments/pool4-mountain-elf-typical-granite-transparent.mdL19(引用正本 0.27 dB)。这正是 #66 要修的后门。 - 保留的 5 条,全部是正本之间互比:
skin-depth-basement(L81/L82/L85)×skin-depth-reference-table(L126/L130/L131/L132)+mountain-elf-typical-granite-transparentL81。与既有 D18/D21/D22 完全对应——basement §2 表花岗岩 δ 32 m → 17.99 km(差 562×),reference-table §三 6 行参数错配,同一根错的两个症状。 - 配对 14→10 而违反只 −1:移出实验设计那 1 点后,与它相关的组合消失。剩下的 10 对全是正本间配对,5 条违反——违反密度不降反升(5/10 vs 6/14),正向化后的信号更干净。
判定逻辑零改动的硬证据:MISMATCH 五行(OK / MISMATCH / param / unit / RANGE)数字全部未变——只改了 _is_quote_doc() 一个函数,R1/R2/R3/R5/R5X 的判读规则、阈值、排除规则一概未动。
五、必须说清的三条边界
第一,违反 6→5 不是”库内矛盾变少”。 是”工具对主张方的判定规则”修正了。库里的错还在原处(5 条违反指向的两处伤口,D18/D21/D22 已登记待 JOE 批)。
第二,本检验只可证伪,不可验证。 比例对得上 ≠ 数值对。R5X 的”通过数”不得进任何质量指标(R11)。剩下 10 对配对、5 条违反——样本量仍不足以推出”全库矛盾率”(R12:分母必须报,且小到不能谈率)。
第三,目录角色规则有一个新的已知盲区。 03-sites/ 内如果有一天出现”审计文”(文件名没命中正则),仍会被当主张方——但这条盲区比”08-ops 实验设计被当主张方”小得多:03-sites/ 是正本落点,按定义该信它、也该审计它。真正要防的是工作区冒充正本,现在由目录结构保证,不再靠文件名猜。
六、证据与局限
外部文献支撑的是公式前提,不是本库数字。
A(dB) ≈ 8.686·d/δ与δ = √(2/(ωμσ))是均匀导电半空间下的标准结果;其在岩石上的适用性受电导率频散限制:Revil (2013, Water Resour. Res., doi:10.1029/2012WR012700) 给出非饱和多孔介质有效电导率与介电常数在宽频段的模型。地物期刊不在 PubMed 收录范围 → 无 PMID → 如实标 E3。
局限(必须与结论同读):
- 本检验判”不相容”仅指跨文件数字不满足
A ∝ d,不指真实地下 A 为另一值,也不指谁的 σ 引用错了。 A ≈ 8.7d/δ假设均匀半空间、无位移电流、μr/σ 为常数。真实山体分层、各向异性、σ 随频率弥散——公式本身在宽频段只是量级估算。- 有效配对仅 10 组、正本仅 6 个文件 27 点,不足以外推任何”全库矛盾率”。
- 只覆盖等式断言;不等式断言与文字区间不参与。
03-sites/内若出现文件名不像审计文的审计文,仍是已知盲区(见第五节)。
免责声明:本文是库内文本一致性的方法学说明,不是地球物理测量结论,不构成任何”靠山能否屏蔽 ELF”的实证判断,更不构成健康或医疗建议。任何据此做的采样决策,须先经 #14 阶段3 实测与 779 终版审核。
七、下一步
- D18 + D1′ + D20 + D21/D22/D23 合并提请 JOE:全部同源(δ 数值错配 → 误判普通花岗岩”值得测” / 高 σ 岩体”无屏蔽”),一次批完,避免分散。
- #68:basement §2 表花岗岩 δ 格 32 m → 17.99 km(5 频点连带)——需与 reference-table 双改(R23:跨文件违反的两端都要查全)。
- 不要再做:R5X 扩成跨材料/跨 μr(物理不成立);词元重叠检测器(第 9 轮证伪);表头正则重写(第 12 轮证伪该归因);区间端点判读(R13);”通过数”当质量指标(R11)。
免责说明:本文属传统知识与科学文献的整理、对照与研究设计讨论,仅供理解与参考,不构成医疗建议,不能替代专业诊断与治疗。文中涉及的效应量、频率区间与暴露结论多为研究报告层面的推断,个体情况差异很大;如有身体不适或健康疑虑,请就医并由专业医师判断。
Who to Trust in Audit Tools: Switching from Filename Guessing to Directory Role Determination (R14 Forwarding)
Evidence level: C
One-sentence conclusion: This repository’s cross-file consistency audit tool, which determines “which file asserts a value and which merely cites it,” previously relied on filename regex (files containing
audit/governance/backlogwere deemed “citing parties”). This approach contained a structural loophole: audit documents, experimental designs, and ledgers were incorrectly classified as “asserting parties” if their filenames did not resemble audit terms—causing the tool to falsely accuse “faithfully recording errors” in ledgers and “faithfully citing originals” in experimental designs, rather than the actual original document with errors. This revision shifts the decision to directory roles:03-sites/is designated as the original (website material drop-off point), while08-ops/serves as the internal workspace (experimental designs, governance cards, ledgers—all citing parties). After this change, cross-file false positives decreased by 1; the remaining 5 violations all point to two known wounds.
I. What This Tool Does
Pool ④ contains a “skin-depth vs attenuation” comparison table (δ-table), which serves as a common baseline for over a dozen downstream studies. To prevent this table from propagating incorrect values, we developed a cross-file scanner (delta-table-scan.py) that performs three functions:
- R1/R2/R3: Extracts δ / A(dB) value assertions from any markdown file and independently recalculates them using the σ/μr values declared within each assertion, determining self-consistency.
- R5 (within-file): If two sets of “thickness vs attenuation” data appear for the same material at the same frequency within one file, their ratio must be equal (
A ∝ d, zero-parameter). - R5X (cross-file): If two files provide mutually incompatible numbers for the same material at the same frequency, report a violation.
R5X is the cross-file version of R5 and represents its first true capture of the repository’s core defect pattern—bilingual mirroring + cross-referenced audit documents, where the same number frequently appears in three places: the original, the audit document, and the backlog.
II. Problem: Filename-Based “Who Asserts” Misidentifies Trusted Documents
R5X initially encountered 32 false positives, reduced to 6 using two rules, one of which is R14 “Citing ≠ Asserting”: audit documents and ledgers list “original value vs recalculated value” side-by-side; these two numbers should differ. Treating them as asserting parties means interpreting “someone cited an incorrect value” as “this file is also wrong.”
However, R14 was originally implemented via filename regex:
Filename contains audit / governance / backlog / report / registry / check / integrity / decision / queue / ledger → not an asserting party
This approach missed two categories of files, both of which should be trusted:
- Audit documents with non-audit filenames (hit in round 17):
pool4-cross-file-a-proportionality-contradiction.mdlacksaudit/backlogin its name, yet it is indeed an audit document—it places the known contradiction “prose 0.27 dB / table 27 dB” side-by-side in the body as an example. The tool treated it as an asserting party, generating 16 false positives. - Experimental designs, governance cards, ledgers (hit in this round):
08-ops/experiments/pool4-mountain-elf-typical-granite-transparent.mdis the accompanying experimental design, which cites the original’s 0.27 dB. Its name contains no audit terms → treated as an asserting party, creating 1 additional violation against the original.
The commonality of these two file types: they are not website originals; they are internal workspaces. Filename regex can never fully guess “which is the workspace”—guessing creates a loophole, and the loophole always catches the most trusted “faithful recorders.” The more faithfully a ledger records errors, the more likely it is to be flagged as erroneous by its own tool—a reverse incentive discouraging thorough documentation, which must be eliminated structurally.
III. Fix: Directory Roles Decide, Filenames No Longer Matter
Shift the “who asserts” decision from “guess via filename” to “determine via directory role”:
def _is_quote_doc(rel):
# True if the real path is not under 03-sites/ (i.e., inside 08-ops/ internal directory) → internal workspace, never an asserting party
if os.sep in rel and not rel.replace(os.sep, "/").startswith("03-sites/"):
return True
return bool(QUOTE_DOC.search(os.path.basename(rel))) # Bare filenames (selftest fixtures) still use regex
The semantics are straightforward:
03-sites/= website material original drop-off point → asserting party (trust its stated numbers; it must be audited).08-ops/(pools / experiments / decisions / ledgers) = internal workspace → citing party (numbers written here cite the original; they are not new assertions, so they do not participate in cross-comparison).- Bare filenames (selftest fixtures, temporary files) → fallback to filename regex (preserve “audit documents are not asserting parties” test semantics).
Why not check frontmatter for pool field: All experimental designs under 08-ops/experiments/ lack pool frontmatter (verified in this round); both approaches yield consistent results. However, directory roles do not depend on whether each file’s frontmatter is complete, avoiding the risk of an experimental design later adding a pool field and silently becoming an asserting party. Directory structure is factual; frontmatter is stylistic—factual structure is more stable.
IV. Test Results: Violations Drop 6→5, Remaining All Original-Original Comparisons
Re-run the same tool on the full repository (--root .):
| Metric | v1.6 (previous round) | v1.7 (this round) | Change |
|---|---|---|---|
| Files hit / total assertions | 52 / 553 | 52 / 553 | unchanged |
| MISMATCH (OK/param/unit) | 297 (208/240/33) | 297 (208/240/33) | unchanged |
| RANGE-unjudged | 48 | 48 | unchanged |
| Table coverage | 63/83 = 75.9% | 63/83 = 75.9% | unchanged |
| R5 violations | 1 | 1 | unchanged |
| R5X violations | 6 | 5 | −1 |
| R5X pairs | 14 | 10 | −4 |
| R5X excluded points | 7 | 8 | +1 |
| selftest | 92/92 | 92/92 | unchanged |
- Eliminated 1 violation:
granite @ 7.83 Hz, where the A-end is experimental design08-ops/experiments/pool4-mountain-elf-typical-granite-transparent.mdL19 (citing the original’s 0.27 dB). This is exactly the #66 loophole to fix. - Remaining 5 violations, all between originals:
skin-depth-basement(L81/L82/L85) ×skin-depth-reference-table(L126/L130/L131/L132) +mountain-elf-typical-granite-transparentL81. These correspond exactly to existing D18/D21/D22—basement §2 table granite δ 32 m → 17.99 km (off by 562×), reference-table §three 6 rows parameter mismatch, same root error manifesting in two symptoms. - Pairs drop 14→10 while violations only −1: removing the experimental design point eliminates its associated combinations. The remaining 10 pairs are all original-original, yielding 5 violations—violation density actually increases (5/10 vs 6/14), making the positively framed signal cleaner.
Zero-change judgment logic evidence: All five MISMATCH categories (OK / MISMATCH / param / unit / RANGE) remain numerically unchanged—only _is_quote_doc() was modified. R1/R2/R3/R5/R5X judgment rules, thresholds, and exclusion criteria remained untouched.
V. Three Boundaries That Must Be Clarified
First, violations dropping 6→5 is not “fewer contradictions within the repository.” It reflects correction of the tool’s asserting-party decision rule. The errors in the repository remain in place (the 5 violations point to two wounds, D18/D21/D22 already logged pending JOE approval).
Second, this test can only falsify, not verify. Proportional matching ≠ numerical agreement. R5X’s “pass count” cannot enter any quality metrics (R11). The remaining 10 pairs and 5 violations—sample size is still insufficient to infer “full repository contradiction rate” (R12: denominator must be reported, and it is too small to discuss rates).
Third, the directory role rule has a new known blind spot. If an audit document appears inside 03-sites/ but its filename does not match the regex, it will still be treated as an asserting party—but this blind spot is far smaller than “08-ops experimental designs being treated as asserting parties”: 03-sites/ is the original drop-off point; by definition, it should be trusted and audited. What truly needs guarding is workspaces masquerading as originals, now ensured by directory structure rather than filename guessing.
VI. Evidence and Limitations
External literature supports formula premises, not repository numbers.
A(dB) ≈ 8.686·d/δandδ = √(2/(ωμσ))are standard results for uniform conducting half-space; their applicability to rock is limited by conductivity dispersion: Revil (2013, Water Resour. Res., doi:10.1029/2012WR012700) provides a model for effective conductivity and dielectric constant of unsaturated porous media across wide frequency bands. Since Earth Science journals are not indexed in PubMed, there is no PMID; thus, label E3 accurately.
Limitations (must be read alongside conclusions):
- This test defines “incompatible” only as cross-file numbers failing
A ∝ d, not implying the true subsurface A is another value, nor that whose σ was cited incorrectly. A ≈ 8.7d/δassumes uniform half-space, no displacement current, constant μr/σ. Real mountain stratification, anisotropy, and σ dispersion with frequency mean the formula itself is only order-of-magnitude estimation across wide bands.- Valid pairs only 10 sets, originals only 6 files with 27 points—insufficient to extrapolate any “full repository contradiction rate.”
- Covers only equality assertions; inequality assertions and textual intervals are excluded.
03-sites/may contain audit documents with non-audit filenames (known blind spot, see Section V).
Disclaimer: This document describes the methodology for textual consistency within the repository, not geophysical measurement conclusions. It does not constitute any empirical judgment on whether “basement can shield ELF,” nor does it provide health or medical advice. Any sampling decisions based on this must first undergo #14 stage 3 measurement and the final review of 779.
VII. Next Steps
- Merge D18 + D1′ + D20 + D21/D22/D23 for JOE submission: all share the same root cause (δ value mismatch → misjudging ordinary granite as “worth measuring” / high σ rock as “no shielding”), so batch them together to avoid fragmentation.
- #68: basement §2 table granite δ grid 32 m → 17.99 km (5 frequencies involved)—requires dual revision of reference-table (R23: both ends of cross-file violations must be fully checked).
- Stop doing: expanding R5X to cross-material/cross-μr (physically invalid); token overlap detector (falsified in round 9); rewriting header regex (round 12 falsified this attribution); interval endpoint interpretation (R13); using “pass count” as quality metric (R11).
Leave a Reply