<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:fh="http://purl.org/syndication/history/1.0"><channel><title>HarnessGrad | News</title><description>The gradient for harness self-improvement: measurable, attributable, comparable.</description><link>https://zjunlp.github.io/</link><language>en</language><fh:complete/><atom:link rel="self" href="https://zjunlp.github.io/HarnessGrad/news/rss.xml"/><item><title>Introducing HarnessGrad</title><link>https://zjunlp.github.io/HarnessGrad/news/2026-10-16-introducing-harnessgrad/</link><guid isPermaLink="true">https://zjunlp.github.io/HarnessGrad/news/2026-10-16-introducing-harnessgrad/</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;HarnessGrad is the gradient for harness self-improvement: the signal a method needs before it
can improve anything, built so the number can be checked rather than asserted. This site is
its front page.&lt;/p&gt;
&lt;div&gt;&lt;h2 id=&quot;what-it-is-for&quot;&gt;What it is for&lt;/h2&gt;&lt;/div&gt;
&lt;p&gt;Every harness-evolution method reports a final score delta. None of them can say what that
delta is &lt;em&gt;made of&lt;/em&gt;, and none report it on a curve a reader can compare against another
method’s. HarnessGrad defines one: a base harness, a fixed task set, a sampling loop, and a
curve point that records the harness state, the two models involved, the score with an
interval, and the compute spent.&lt;/p&gt;
&lt;p&gt;The repository proposes no RSI method. It ships runnable reference methods, but the
contribution is the instrument that decides whether any of them worked — and it measures
every candidate itself, because a subject that scores itself makes the comparison
meaningless.&lt;/p&gt;
&lt;div&gt;&lt;h2 id=&quot;what-runs-today&quot;&gt;What runs today&lt;/h2&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The local demo&lt;/strong&gt;, end to end, with zero network and zero cost.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The measurement contract&lt;/strong&gt;, written down as &lt;code dir=&quot;auto&quot;&gt;INTERFACE.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Enforced isolation&lt;/strong&gt;: a harness cannot see the platform while it runs, and runs made
under different isolation rules are never placed on one axis.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Per-dataset tests&lt;/strong&gt;, so one change does not require the whole suite.&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;&lt;h2 id=&quot;what-is-not-claimed&quot;&gt;What is not claimed&lt;/h2&gt;&lt;/div&gt;
&lt;p&gt;Local results are not production evidence, and a demo or diagnostic grants no production
authorization. Per-dataset gaps in runtime, quota, snapshot and cleanup enforcement are
recorded with a disposition rather than smoothed over.&lt;/p&gt;
&lt;p&gt;No dataset has been chosen, and the metric is defined no further than “defined on a task
set and pairable”. Contamination — whether the agent model has seen the benchmark tasks —
is not detectable from inside the framework, and is the largest known threat to the
validity of any curve.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://zjunlp.github.io/HarnessGrad/getting-started/&quot;&gt;Getting started&lt;/a&gt; runs the demo.
&lt;a href=&quot;https://zjunlp.github.io/HarnessGrad/status/&quot;&gt;Status and limits&lt;/a&gt; is worth reading first.&lt;/p&gt;
</content:encoded></item></channel></rss>