Answer first
The question map gives each common ModelBreeder question one short answer, one canonical route, and a few supporting routes. It is designed for readers first and answer systems second.
High-value questions
What is model breeding?
Model breeding is the disciplined creation, comparison, and reuse of model descendants so capability can compound through useful specialists, trusted evidence, local execution, and human-guided evolution.
Canonical route: Model breeding foundations
Why use a population instead of one large model?
A population can preserve specialists, run cheaper local paths, compare alternatives, keep useful diversity, and release improvements with clearer lineage.
Canonical route: Model ecology vs monolith
What is Apex Multi Model?
Apex Multi Model is a governed, reversible, evidence-bearing model ecology where specialists, descendants, adapters, routers, evaluators, lineage records, release gates, and human review layers produce more value together than one model can alone.
Canonical route: Apex Multi Model
What is a fitness proof?
A fitness proof is the evidence bundle showing that a descendant improves a declared niche under a declared budget, while preserving lineage and a rollback target.
Canonical route: Fitness proof
How does model merging fit model breeding?
Model merging is one breeding operator. It combines compatible trained models, task vectors, or adapters into a descendant that must be compared against its parents and alternatives.
Canonical route: Model merging upside
What should a first model-breeding lab build?
Start with one parent, one bounded operator, one frozen evaluation set, one manifest, one scorecard, one lineage record, and one reversible release packet.
Canonical route: Model-breeding lab v1
Where are the source reports?
The reports are preserved in /docs inside the ZIP and rendered publicly through the Research Library. Direct /docs access is blocked by the server rules.
Canonical route: Research Library
Is this a WordPress site?
No. ModelBreeder.com is a plain vanilla PHP, file-backed, root-extractable site with no database and no WordPress artifact target.
Canonical route: Plain PHP package contract
Machine-readable companion
The generated JSON companion lives at:
/assets/data/canonical-answers.json
The JSON is generated from the same route map and is advisory only.
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.