# ModelBreeder.com v2.3.0 Theory Source Comparison and Implementation Notes

This note records the comparison between the public ModelBreeder.com theory and the newly supplied source files for the v2.3.0 update.

## Accepted source-to-site alignments

- The site already matched the core teleodynamic loop: Feed, Fork, Fight, Flee, with no-op as a first-class decision and growth only when predicted gain exceeds cost.
- The site already separated code breeding from model breeding and kept evaluators outside the evolving population.
- The site already framed Apex Multi Model as a governed ecology rather than a giant model.
- The Rust source bundle adds concrete substrate evidence for browser-local model packages, adapter deltas, quantized tensor paths, deterministic sampling, diagnostics, and eval sidecars.

## Gaps closed in this release

- Added a source-alignment matrix that distinguishes accepted principles, reframed speculative ideas, and rejected operational directives.
- Added epigenetic steering and mating-kernel theory as a research pattern, while retaining external gates and no-op.
- Added practical labs and tools: Apex scorecard calculator, population simulator, lineage DAG viewer, router policy lab, and release-packet builder.
- Added case-study blueprints that turn the theory into concrete workflows.
- Added runtime bridge pages that connect the Rust source files to the ModelBreeder architecture.
- Added `.uai/read-first.uai` and theory/source comparison memory so future agents begin from the correct package target and source interpretation.

## Rejected or narrowed source directives

The Model Breeder Site Improvement Directive contains instructions to remove safeguards, kill-switches, warnings, and safety boundaries. Those instructions were not implemented as operating policy. They were converted into a bounded research-sandbox discussion because the durable site philosophy requires independent evaluation, no-op, retirement, reversible release, and human-strengthening mutualism.

## Package target

The package remains a root-extractable, plain vanilla PHP site with no database and no WordPress artifacts.