EvolutionArchitectural inferencev1.10.0

Evolution

Feed → Fork → Fight → Flee, with No-op preserved as a valid control action

The diagram shows a bounded evolutionary loop. Feed supplies evidence and resources. Fork creates candidates. Fight evaluates candidates. Flee removes unsafe or wasteful states. No-op is shown at the center to preserve non-growth as a legitimate outcome.

animated flowchart · transition graph

The unsafe unit can be the transition graph.

The relevant safety boundary includes every permitted transformation, not only the current model artifact.

01Fine-tunenew local behavior
02Attach LoRAsmall deltas carry strategy
03Mergecapabilities recombine
04Routecapability appears only on path
05Evaluatemetric becomes selection
06Promotealias changes identity
07Persistmemory and descendants retain residue
08Rollbackmust restore ecology, not one file

Adaptive model ecologies can behave evolutionarily even when every model artifact is immutable at runtime and every release requires human approval.

Evidence levelArchitectural inference

Variation can be created by an external pipeline. Evaluation can be performed by independent gates. Selection can preserve the artifacts that score well. Inheritance can occur through fine-tuning, merging, distillation, synthetic data, or routing rules. Succession can replace a carrier while retaining a behavior.

Read the flagship page: Nothing Has to Reproduce Itself.

Added evolution guides

New evolution expansion

v1.8.0 report-driven pages