Peter Chen, Ni Zhang, Ying Xu, Siyuan Zhang
Carefully reported, honest audit with reusable protocol and positive controls, but limited by an easy single target, two-system case-level depth, and largely expected findings.
Agent systems built on local large language models are increasingly marketed through the vocabulary of cognitive architecture: modules named global workspace, theory of mind, causal reasoning, or active inference are listed as features, and the presence of the name is taken as the presence of the mechanism. We ask the prior question -- does the named computation actually happen -- and contribute a transferable verification method for the claim-implementation gap: a four-question static audit protocol with line-number evidence and call-chain tracing, demonstrated on two systems. We audit a system claiming 25 cognitive mechanisms, pre-register falsifiable predictions for 11 modules and execute the interventions, replicate the protocol on the IIT-phi core of a second, independent system with its own pre-committed falsification criteria, and run two repair experiments as positive controls. In 18 of 25 modules the computed value never reaches any production output; three idle-wiring shapes new to the dead-code and code-smell literatures emerge (connected-but-never-called, called-but-inert, called-but-content-blind). Of 61 frozen criteria across 12 interventions, 53 were confirmed, two partially adjudicated, five falsified, one adjudication-ambiguous. Repairs raised planner task success from 0.028 to 1.000 and cut state-controller error by 52%. Module names and module computations must be audited as independent claims; the protocol and the five-class failure taxonomy are reusable for the claim-implementation gap at two-system, case-level depth.
The paper audits whether "cognitive-architecture" module names in an LLM-agent repository correspond to computation that reaches output. It offers four things:
The headline findings are that 18 of 25 modules never affect production output, and that none of the 7 partial modules influences control flow. Repairs raised planner success from 0.028 to 1.000 and cut controller error by 52%. The framing is useful: a module name and the computation behind it are independent claims. The authors openly say the findings are mostly visible from reading code, so the contribution is quantification and protocol rather than surprise.
Strengths:
Weaknesses:
The protocol is simple and portable, and the call for mechanism-level checks in artifact evaluation is sensible. It could be cited in discussions of AI-agent hype, artifact evaluation, and consciousness-claim skepticism. The idle-wiring shapes are somewhat useful vocabulary, though their claimed novelty relative to dead-code and data-flow analysis is modest. The most likely path to influence is as a case study or template within the reproducibility and agent-evaluation communities. The paper is unlikely to shift mainstream agent research, since the audited systems are fringe, but it models good practice for negative-result reporting.
Agent systems with anthropomorphic module names, and consciousness-related claims about AI, are a current concern. Claim-versus-implementation gaps are a real problem, and a cheap audit method is relevant. However, an automated or LLM-assisted static audit of this kind will probably be superseded by general code-analysis tools. The paper also reads somewhat like a prolific self-citing series, with companion audits cited as preprints on Zenodo.
Strengths:
Limitations:
This is a competent, honest, and modestly useful methodological case study. Its scientific impact is limited by the weak target, the narrow scope, and the near-tautological nature of many findings, but it has value as a template and as a cautionary data point.
Generated Nov 2, 2026
Carefully reported, honest audit with reusable protocol and positive controls, but limited by an easy single target, two-system case-level depth, and largely expected findings.