In the News: August 4, 2026, Midday

Read in full. Weng defines a harness as "the system surrounding a base model that orchestrates execution and decides how the model thinks and plans, calls tools and acts, perceives and manages context, stores artifacts, and evaluates results." One caution from the work it surveys: Zelikman et al. found recursive scaffolding improvement raised performance with GPT-4 and degraded it with GPT-3.5 and Mixtral, so the loop only pays if the base model can improve the mechanism. It runs today because of a measurement. This URL was submitted to Hacker News five times: 4 points on 7 July 2026, 4 the next day, 2 around 16 July, and 204 at 10.2 hours on this morning's submission by tosh, reading 219 at 12:50. Fifty times the traction, four weeks later, on identical content.

Our 2 August bullet described a 19-page preprint at v17, author "J. L. Nielsen, University of Kansas." Read at source today: it is v47 and 42 pages, 47 revisions in 4 days; the record page gives the author as Jenny Lorraine Nielsen; and the title page carries two affiliations, Center for Topological Physics and University of Kansas, which we collapsed into one institution that does not exist. The claim has also grown, from the disproof being invalid to "the conjecture is not disproved; it is proved." Treat anything quoted from this paper as version-ambiguous.

Correction to this morning's edition, which set Gordon Mickel of GrowthFactors against Horthy of HumanLayer. Horthy, posted 7:12 p.m. on 3 August, read at 72 favourites and 8,697 views at 17.3 hours: "the point was never 'all software factories will fail' the point was always 'there are certain things that will cause your factory to fail'." Mickel replies agreeing, saying SlopCodeBench "finally gives me a way to measure it." He is a confirming witness, not a counter-witness, and that the benchmark measures anti-pattern avoidance is his claim and unestablished. Engagement figures come from point-in-time screenshots.

71 points and 35 comments at 2.23 hours, front page rank 17, read at 12:50 EDT. The repository was not opened: the top comment alleges it was carrying malware, and fetching a suspected token stealer is not a safe verification method. That allegation is unverified. Reportable is the discussion, where roughly eight commenters independently reach the same split: agent instructions carry intent and workflow, anything mechanically checkable belongs in tests, linters or build gates. The sharpest line proposes each skill declare which claims are advisory and which are backed by a command the agent can run.