Self-improving systems

Type: types/tag-readme.md

A self-improving system makes operative, evidence-responsive changes to its own behavior-determining organization, read against a declared frame of boundary, horizon, and improvement objective. Assign this tag to work on whether or how systems make such changes: their definition and classification, mechanisms, limits, or evidence of improvement. Ordinary task execution or automation is insufficient without that question. Tagging an analysis does not certify that the analyzed system improves. The child areas below cover the specific mechanisms and tests. Deploy-time-learning covers the post-release demand for change, including changes made by human maintainers; learning-theory covers learning more broadly, whether or not the learner changes its own organization.

Child areas

  • theory-builder — the theory-builder definition and its companions: tentative and addressable theory, retained theory guiding search, theory fit and warrant, the Popperian precedents; the research program Commonplace runs
  • software-factory — factories and houses: family-specific production machinery, factory development and learning, universality, task versus product families
  • improvement-loop — the proposal-selection architecture: search control, what to learn, oracle accumulation, diagnostic richness, false-positive filtering, omitted versus frozen loop functions
  • reflection — reflective systems: addressability, second-order lessons, graded coverage, retrieval misses, Gödel machines, and the Commonplace reflective-trace evidence
  • warranted-autonomy — which decisions a computational actor is warranted to take over from humans, the oracle domain that bounds it, closure, and measuring autonomy
  • continual-learning — how a deployed system keeps learning outside model weights: the readable-artifact loop, form coevolution, governing writes, and the Bitter Lesson defense of that bet

Definition and objective

Accumulation and compounding

Casebooks and records

  • deploy-time-learning — the phenomenon: deployment forces post-release change, historically the maintainers' work
  • learning-theory — the parent area for how systems learn; the six children above are also its routes into self-revision
  • computational-model — the execution substrate these systems run on

Other tagged notes