Superintelligent Software Engineering: Governance That Scales with Capability

cs.SE cs.AI Mohammad Mehdi Gholinejad · Oct 22, 2026
Local to this browser
What it does
The paper defines superintelligent software engineering as the discipline of building software with agents that exceed human reviewers, arguing that raw capability is necessary but insufficient without governance that scales mechanically....
Why it matters
An exploratory snapshot of 452 popular GitHub repositories finds widespread stale agent context files, and the paper introduces OSTEON, a released discipline of governed knowledge repositories, mechanical gates, and decay control. The...
Main concern
The paper is an honest, tightly scoped vision piece that makes a conceptual case for scaling governance with agent capability. Its formal escape model offers useful intuition, but the author correctly labels it illustrative rather than...
Community signal
0
0 up · 0 down
Sign in to vote with arrows
AI Review AI reviewed
Plain-language introduction

The paper defines superintelligent software engineering as the discipline of building software with agents that exceed human reviewers, arguing that raw capability is necessary but insufficient without governance that scales mechanically. It proposes that correctness depends on decisions and contracts outside the code, that such knowledge decays, and that once agent throughput $r$ outstrips fixed human review capacity $c$, the share of stale-built changes caught by reading falls toward zero. An exploratory snapshot of 452 popular GitHub repositories finds widespread stale agent context files, and the paper introduces OSTEON, a released discipline of governed knowledge repositories, mechanical gates, and decay control. The author commendably marks OSTEON's unmeasured claims as opinion and frames a falsifiable research agenda.

Critical review
Verdict
Bottom line

The paper is an honest, tightly scoped vision piece that makes a conceptual case for scaling governance with agent capability. Its formal escape model offers useful intuition, but the author correctly labels it illustrative rather than empirical, and no experiment evaluates whether OSTEON actually reduces stale-built changes. The exploratory repository measurement is methodical and pre-registered, yet it only checks path resolution in context files, not whether stale knowledge harms agents or whether OSTEON would help. As a research agenda and conceptual framework it succeeds; as evidence for a working discipline it remains speculative.

“It is a model, not a measurement.”
Gholinejad, Sec. III-C · Section III-C
“The paper reports no measurement of OSTEON’s effect, so nothing here shows that the discipline works; it shows what it does and why we expect it to matter.”
Gholinejad, Sec. XII · Section XII
What holds up

The paper’s definitional work is rigorous. The three-regime taxonomy—assisted, delegated, and superseded—clearly separates human-verified, capped-delegation, and outpaced-throughput scenarios, and the escape model in Eq. (2) formalizes why capability alone cannot lower the stale-built escape rate once $r > c$. The author is admirably transparent: the research agenda states falsifiable claims with refutation conditions, every opinion and practice heuristic is explicitly bracketed, and the GitHub snapshot follows a pre-specified protocol with released scripts and sensitivity audits.

“A vision earns its keep by saying what would prove it wrong. We state the thesis as testable claims, with the evidence that would refute each...”
Gholinejad, Sec. XI · Section XI
“The frame, the file list and the metrics were written down verbatim, in the study’s protocol and in the header of the collection script, before collection began.”
Gholinejad, Sec. IV · Section IV-A
Main concerns

The central problem is that OSTEON is proposed but never tested. Section VI-H candidly notes that OSTEON’s own development did not apply the discipline to itself—there are no decision records, no bone repository, and capture stopped weeks before the last commit. The escape model assumes independent staleness and fixed review capacity, assumptions the author admits are violated in practice, and it understates the problem by holding $s$ fixed when agent changes themselves raise staleness. While the 9.5%–22% dangling-reference rate in context files is an interesting symptom, unresolved paths are not proven defects; the leap from unresolvable paths to harmful agent behavior remains speculative. Because the seven requirements were co-designed with OSTEON rather than derived independently, they risk rationalizing the proposed solution rather than grounding it in comparative evidence.

“The history shows the mechanisms in partial use by their designer and nothing more, and we report it for that reason.”
Gholinejad, Sec. VI-H · Section VI-H
“The model assumes independent staleness, a fixed review capacity and a fixed detection probability. Real projects violate all three.”
Gholinejad, Sec. XII · Section XII
Evidence and comparison

The positioning against related work is fair and precise. The paper distinguishes itself from SE 3.0 and agentic software engineering by focusing on the superseded regime where humans cannot read every change, and it correctly cites Gloaguen et al. to support the claim that ungoverned context files do not generally improve task success while raising inference cost by over a fifth. The comparison to ContextNest and Deliberative Curation is nuanced, acknowledging complementarity. However, there is no comparative evidence that OSTEON outperforms simpler baselines—such as better-maintained context files, stricter review caps, or lightweight linting—and while the paper frames Gloaguen et al. as supporting the currency hypothesis, that causal interpretation is explicitly marked as the author’s own addition rather than the study’s finding.

“we find that providing context files does not generally improve task success rates, while increasing inference cost by over 20% on average.”
“Gloaguen et al. found that providing context files such as AGENTS.md does not generally improve task success, while it raises inference cost by over a fifth on average.”
Gholinejad, Sec. X · Section X
“a first step toward training superintelligent software engineering agents that learn from their own experience”
Reproducibility

Reproducibility is unusually strong for the exploratory measurement: the protocol, collection scripts, dataset, and sensitivity audit are all released as ancillary files, and the per-file statistics can be recomputed from the released artifacts. OSTEON itself is archived on Zenodo with a DOI and an open license. However, the core claims about governance scaling cannot be independently reproduced because no evaluation protocol, benchmark results, or effect sizes are provided; the paper explicitly reports no measured effect of OSTEON. The chief barrier is the absence of an empirical evaluation against the falsifiable questions Q1–Q6, which the paper honestly states as future work.

“The scripts, the per-file data and the per-candidate evidence are released, so every per-file statistic can be recomputed;”
Gholinejad, Availability · Availability
“It reports no measurement of OSTEON and claims no measured effect.”
Gholinejad, Evidence status · Evidence status
Abstract

Software agents are being trained to exceed human engineers; we argue that capability alone does not produce better software engineering. We define superintelligent software engineering as the discipline of building and evolving software with agents whose capability exceeds that of human engineers, in which governance (gates, contracts, decisions and decay control) scales with capability. The argument rests on three claims. First, correctness in a project rests on decisions and contracts that the code does not carry. Second, knowledge decays. Third, once an agent outpaces its reviewers, reading catches a shrinking share of the changes built on stale knowledge. A simple model shows that, past a fixed review capacity, escaping changes grow linearly with throughput while the share that reading catches falls toward zero; governance can lower the slope, capability alone cannot. An exploratory snapshot of 452 of the most-starred public GitHub repositories finds a root-level or .github agent context file in 48.67% (95% confidence interval 44.1 to 53.3); in the median file that names repository paths, 9.5% to 22% of those paths do not resolve, depending on how a reference is read. We then present OSTEON, a discipline for the regime, released with a DOI (10.5281/zenodo.23436020): each project gets a governed knowledge repository of decisions and contracts, every change is checked mechanically against it, and the knowledge itself is checked for decay at every session start; planning is gated, and sessions record what they learn without writing rules. We report no measured effect of OSTEON, mark claims about its mechanisms as opinion and the author's practice heuristics as design rationale, and state the questions that would falsify the thesis.

Challenge the Review

Pick a starting point or write your own. Challenges run in the background, so you can keep reading while the AI investigates.

No challenges yet. Disagree with the review? Ask the AI to revisit a specific claim.