mlsanityData to 14 Oct 2026

The Substrate Collapse: AI Code Generation Invalidates Authorship-Based Knowledge Metrics

arXiv 2606.20882 ↗First posted 18 Jun 2026cs.SE cs.AIcited by 0

Not on the map. Why?

Abstract (arXiv)

Software engineering has long inferred where a system's knowledge resides from who authored its code. The truck factor, the Degree-of-Authorship metric, and the degree-of-knowledge model all rest on one inference -- that authoring a region of code is evidence of understanding it -- and for most of software's history it was a workable proxy, because code entered a repository only when a human wrote it, which forced at least transient understanding. This paper argues that AI code generation severs that inference at its root, and that the consequence is not the degradation of the authorship-based metrics but their invalidation as a class. When an agent generates a module and a human merges it, the version-control record still attributes authorship, but the attribution no longer licenses any conclusion about comprehension: the same footprint is now compatible with full, partial, or no understanding. The metric still returns a number; the number measures a substrate that has come uncoupled from the quantity it was used to estimate. The collapse is corroborated by the field's own measurement failures, and the methodological corollary is load-bearing: the instrument the comprehension-debt era needs cannot be built by refining the knowledge-concentration metrics, because no function of an authorship footprint recovers an inference the footprint no longer supports. The replacement must be grounded in evidence of comprehension rather than authorship. I state a falsifiable prediction that discriminates the two -- that systems with a healthy authorship-derived truck factor but low comprehension-measured retention will suffer incident-resolution failures the authorship metric does not predict -- and argue that building the comprehension-grounded instrument at the scale of a system and a team is the field's open measurement problem, left open here.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 11 of its 23 references that are in the map. First posted on arXiv 18 Jun 2026.

Builds on

11 of 23 references.

References · 11

  1. 2025Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivitycited by 101
  2. 2025A.S.E: A Repository-Level Benchmark for Evaluating Security in AI-Generated Codecited by 14
  3. 2026Debt Behind the AI Boom: A Large-Scale Empirical Study of AI-Generated Code in the Wildcited by 10
  4. 2016A Novel Approach for Estimating Truck Factorscited by 6
  5. 2026From Technical Debt to Cognitive and Intent Debt: Rethinking Software Health in the Age of AIcited by 6
  6. 2025AI Code in the Wild: Measuring Security Risks and Ecosystem Shifts of AI-Generated Code in Modern Softwarecited by 4
  7. 2025Is Your Prompt Poisoning Code? Defect Induction Rates and Security Mitigation Strategiescited by 3
  8. 2026Mitigating "Epistemic Debt" in Generative AI-Scaffolded Novice Programming using Metacognitive Scriptscited by 2
  9. 2026Comprehension Debt in GenAI-Assisted Software Engineering Projectscited by 2
  10. 2025NRevisit: A Cognitive Behavioral Metric for Code Understandability Assessmentcited by 1
  11. 2025Reflection-Driven Control for Trustworthy Code Agentscited by 1

Built on by

Not cited yet.