Reflection makes retained lessons second-order: a lesson can reject or rescope a prior commitment

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

Retained lessons are learned inductive commitments: they shape how the system generalizes from future evidence. Reflection changes which objects a new lesson can target. When a prior commitment and its applicability conditions are represented and addressable, a later lesson can operate on that commitment explicitly — rejecting, revising, or rescoping it. Without that addressable object, correction still occurs, including large or abrupt parametric updates, but only indirectly through operations on the substrate.

Indirect correction without an addressable commitment

A non-reflective pathway can transform behavior through gradients, parameter replacement, model editing, or other substrate-level updates. Those changes need not be small, additive, or globally uniform; learned context-sensitivity can make their effects conditional. What the pathway lacks is an internal operation whose target is the prior commitment as a represented commitment. “Reject this rule” and “narrow its stated applicability boundary” are unavailable unless some representation exposes that rule and boundary to the system's own processes.

Second-order retention: lessons about commitments

Route retention through a causally connected self-representation and prior commitments become addressable objects, since reflection buys addressability. Then a new lesson can be retained as an operation on a commitment rather than alongside it:

  • Rejection — the theory is discarded, and its entire explanatory-reach goes with it in one step: every future episode it would have governed is re-opened at once.
  • Rescoping — the theory survives with its applicability boundary redrawn: "this holds" becomes "this holds for cases like these", or a boundary found too tight is widened.
  • Revision — the content itself is corrected in place, keeping the commitment's identity and history.

A worked instance: a system retains the commitment "skip integration tests when only documentation files changed," formed after several doc-only PRs proved harmless without them. Rejection discards the commitment outright the first time a doc-only PR breaks a build that reads one of those files as config — every future doc-only PR goes back through the full suite. Rescoping narrows the boundary instead: "skip integration tests when only documentation files changed, except files under build-tooling paths." Revision leaves the boundary alone and corrects the prescription itself: "skip integration tests, but still run the docs-lint check." Same retained artifact, three different single-step operations on it — a first-order pathway has none of them; it can only accumulate more evidence about when doc-only changes are safe.

These operations can change behavior across the commitment's explanatory-reach in one explicit revision. That supplies a mechanism for selective correction and targeted rollback; whether it improves target-data efficiency is the downstream, conditional conjecture in reflective theory refinement needs both interpretation and retention from one substrate.

Rescoping requires represented scope

Opaque commitments can have highly conditional effective scope, but that scope is not necessarily exposed as a separately inspectable boundary. A reflective artifact can state applicability conditions, retrieval can restrict where it loads, and a later lesson can rewrite the represented boundary directly. The distinction is addressability of scope, not global versus local behavior.

One dependency from the aspect-bounded nature of reflection: rejection requires only that the commitment's content be addressable, but rescoping requires its scope to be a represented aspect — a system that retains legible rules without stated boundaries can discard a theory yet cannot narrow one. Second-order retention is therefore graded by the same aspects reflection exposes.

Scope

  • The claim is about available operations, not outcomes. A second-order lesson is itself a commitment and can be wrong: a mistaken rejection discards a good theory with all its explanatory-reach, so the same lever that makes correction cheap makes damage cheap. Nothing here says second-order changes are more often correct — acceptance remains an improvement claim, not evidence of improvement. What would make them more often correct is reach-assessment on the evaluator's part, which reflection's structural operations do not supply by themselves.
  • Parametric pathways can produce analogous behavioral effects through machine unlearning, targeted fine-tuning, activation steering, or model editing. The distinction claimed here is whether the system's own retained lesson targets a represented commitment, not whether non-reflective machinery can achieve the same outcome.

Open Questions

  • Whether second-order operations measurably beat first-order counter-training at matched evidence — the per-operation form of the target-data conjecture, and testable the same way.
  • Whether rescoping or rejection dominates in practice in deployed agent memory systems, and whether any current system represents scope well enough to rescope at all rather than delete and rewrite.
  • Whether there are third-order lessons worth naming — lessons about the system's rejection and rescoping policies themselves — or whether those collapse into second-order operations on the improvement process's own commitments.

Relevant Notes: