Foundations Introductory 2 minute read Updated 2026-06-26 UTC

Research maturity map

A disciplined map of which ideas are established engineering, emerging research, conceptual synthesis, or speculative extension.

Research statusEditorial policy Publication statePublished Reviewed byMichael Kappel Source reports3

Why maturity labels matter

The source corpus intentionally ranges from practical system design to long-horizon speculation. A high-quality engineering site should not flatten those categories. The same page can discuss an established technique such as distillation, an emerging technique such as automated model merging, and a conceptual governance model such as teleodynamic viability. Readers need to know which claims are operationally mature.

The site marks each idea by maturity rather than presenting every source claim as established fact.

Maturity categories

CategoryMeaning on this siteExamplesAppropriate use
Established engineeringWell-known methods with repeatable implementations and substantial literature.Ensembles, distillation, quantization, pruning, federated averaging, model registries, canary delivery.Production with normal domain validation.
Emerging practiceActive research or early production practice with incomplete standards.Automated model merging, learned routers across heterogeneous specialists, quality-diversity for model portfolios.Controlled pilots and benchmarked experiments.
Conceptual synthesisA useful organizing framework assembled from existing methods but not yet a canonical field term.Model breeding, code breeding, digital Four Fs, teleodynamic controller, model ecology.Architecture communication and research design.
Speculative extensionScenario analysis whose assumptions exceed current evidence or capability.Open-ended autonomous self-modification, intrinsic survival drives, cosmic replication scenarios.Risk analysis and philosophy, not implementation requirements.

Evidence rules used by the curated guides

  1. A metaphor is never treated as proof of mechanism.
  2. A source-report claim is not promoted to established fact merely because it includes a citation list.
  3. Exact benchmark numbers are omitted unless independently verified for the intended decision.
  4. Future-dated or rapidly changing claims should be rechecked against primary sources before publication.
  5. Architecture guidance favors techniques that remain valuable even when speculative claims are false.
  6. Safety controls are applied to the capability envelope, not to assumptions about consciousness or intent.

What remains valuable under uncertainty

Even if model breeding never becomes standard terminology, the underlying engineering agenda remains coherent: versioned specialists, immutable lineage, independent evaluation, multi-objective selection, resource-aware routing, reversible structural change, and explicit governance. These are durable system properties.

How to read raw reports

Use raw reports to trace conceptual origins, compare narratives, and locate references. Treat them as research inputs rather than production specifications. The editorial method explains how the site converts overlapping reports into normalized guides, while research status documents known limitations and duplication.

Source reports used for this guide

These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.