Diagnostic richness constrains outer-loop learning quality
Type: kb/types/note.md · Tags: learning-theory, deploy-time-learning
Outer-loop learning improves a system by proposing candidate changes, evaluating them, and feeding the result into the next proposal. This note distinguishes two separable evidential bottlenecks in that loop. The oracle decides which candidates deserve promotion. Diagnostic richness decides what the proposer can infer from previous attempts before generating the next candidate. Proposer capability and search policy also matter, but they are separate from the evidence surfaces this note isolates.
Diagnostic richness is the amount and structure of retained evidence available for explanation: scores, diffs, traces, tool calls, memory state, candidate files, frontier state, and drill-down paths back to raw evidence. Frontier state means the current-best candidate set or ranking maintained by the search loop. A strong oracle can rank candidates without explaining why they worked. A rich diagnostic substrate exposes mechanisms: which tool failed, which prompt branch activated, which memory item was read, which candidate changed behavior, and which failure mode repeated.
That makes diagnostic richness orthogonal to oracle strength. Oracle strength names the quality and cost of selection. Diagnostic richness names the quality of the search context. Scores-only feedback can support promotion, but it gives the next proposer little basis for hypothesis formation. Raw traces and structured derived views cost more context, but they let the proposer search through causes rather than only outcomes.
Meta-Harness, a framework for optimizing task-specific model harnesses, makes the gradient concrete through its online text-classification ablation. Every proposer arm could inspect prior scores and code. The Scores Only arm reached 34.6% median accuracy, the Scores + Summary arm reached 34.9% without traces, and the full arm reached 50.0% with traces. The fixed summary treatment therefore did not recover the trace-access arm in this setup. These are point summaries, and the experiment tests one trace-removing summary treatment rather than summaries or abstraction in general. The bounded result supports this note's claim that a proposer cannot exploit diagnostic information it does not receive; it does not license the stronger instruction to "load everything."
AutoSaddler supplies a second bounded contrast. In its GAIA2 test, removing in-depth diagnosis reduced reported Pass@1 from 62.0% to 57.8%. The ablation replaced a diagnosis stage that could inspect execution traces and harness source code with one LLM call given an execution trace and evaluation results; its inferred failure reason then returned to CA-SDK for patch generation (AutoSaddler). The experiment therefore tests one code-and-trace-access treatment against one shallow-call treatment within a fixed optimizer and harness update space. It supports the narrower claim that diagnostic access can affect this loop's results, but it does not isolate which additional signal or investigation operation caused the gain or show that more diagnostic context is always better.
Richness still needs staging. Agentic Harness Engineering, an observability-driven coding-agent harness evolution loop, keeps raw traces available but normally feeds root-cause reports first to the evolve agent, the component that proposes harness changes. HALO, a trace-analysis engine for agent harnesses, indexes byte offsets, exposes bounded trace tools, returns summaries for oversized traces, and preserves drill-down paths to raw evidence. These systems treat summaries and indexes as navigation surfaces, not as replacements for evidence.
For KB and harness-learning loops, the design implication is direct: keep selection signals and diagnostic surfaces separate. A frontier file, score table, or review decision can tell the next agent what won; it cannot by itself tell the agent what to try next. Durable learning loops need enough retained evidence for later proposers to form causal hypotheses, plus enough progressive disclosure from summaries to raw evidence to keep that evidence affordable inside a bounded context.
Relevant Notes:
- oracle strength spectrum — contrasts: oracle strength names candidate selection quality, while diagnostic richness names proposal evidence quality
- Trace-learning techniques in related systems — evidenced-by: survey paragraph and Meta-Harness ablation ground the diagnostic-richness axis
- Ingest: Meta-Harness: End-to-End Optimization of Model Harnesses — evidenced-by: retained ablation extracts supply the three accuracy figures and the source's comparison between trace access and summaries
- Ingest: AutoSaddler: Automatic Harness Optimization with Durable Updates — evidenced-by: its GAIA2 diagnosis ablation bounds the claim to one code-and-trace-access treatment against one shallow-call treatment
- Meta-Harness — exemplifies: its proposer reads prior results and traces from retained run files when forming and implementing candidate changes
- Agentic Harness Engineering — exemplifies: root-cause reports compress traces while keeping raw evidence available for audit
- HALO — exemplifies: bounded trace tools preserve drill-down from summaries and indexes to raw spans