Evidence bearing on an improvement objective

Type: kb/types/definition.md · Tags: foundations, self-improving-systems

Evidence bears on an improvement objective when it carries information about how the system stands relative to that objective, and a change is responsive to it when the evidence causally shapes the change — what is changed, how much, or whether it is kept. This is the clause that makes a self-improving system's changes improvement-directed rather than merely caused, and it is deliberately indifferent to architecture.

Scope

The evidence can be any signal diagnostic of the criterion:

  • gradients and error signals — derived from a loss the objective defines;
  • rewards — returns from an environment against a reward function;
  • viability signals — essential variables leaving or re-entering declared bounds;
  • test results, proofs, and validator verdicts — mechanical checks against a stated contract;
  • measurements and usage traces — observed performance, incidents, benchmark outcomes;
  • human judgments — review verdicts, maintainer standards, rubric applications.

The evidence does not need to appear in a separate evaluator component. In direct-determination pathways the update rule consumes it wholesale — the gradient step is the response. Only the proposal-selection subtype implements the criterion as a gate that consumes evidence to accept or reject.

Exclusions

  • Uninformative triggers. A timer, a fresh request, an unconditional event — these cause changes without carrying any information about the objective. Change on trigger alone is self-modification, not self-improvement.
  • Idle evidence. Evidence that exists but does not causally affect the change makes nothing responsive; a dashboard nobody's update rule or judgment consumes bears on the objective and changes nothing.
  • Evidence of the wrong thing. A signal diagnostic of some other criterion can drive changes that are responsive — to that other objective. Which objective the evidence bears on decides what the system is directed at, and directedness is all it decides.

Misuse Cases

  • Treating any input the system reacts to as improvement evidence — reaction is not responsiveness to a criterion.
  • Requiring the evidence to flow through an explicit gate — that is the subtype's architecture, not the semantic requirement.
  • Reading evidence-responsiveness as evidence of improvement — a faithful response to a mis-specified objective degrades the system exactly as responsively.

Relevant Notes: