Reference All levels 2 minute read Updated 2026-06-29 UTC

Entity Catalog for ModelBreeder.com

Stable names, definitions, canonical routes, source evidence, and supporting pages for the core ModelBreeder.com topic graph.

Research statusGenerated topic map plus editorial synthesis Publication statePublished Reviewed byMichael Kappel Source reports9

Answer first

The entity catalog is the site’s controlled vocabulary. It tells readers and machines which page owns each concept, which pages support it, and which source reports back it.

Core entities

EntityCanonical routePlain definition
Model breedingModel breeding foundationsDisciplined creation, comparison, and reuse of model descendants so capability can compound.
Apex Multi ModelApex Multi ModelA governed population of specialists, descendants, adapters, routers, evaluators, lineage records, and release packets.
Fitness proofFitness proofEvidence that a descendant improves a declared niche under a declared resource budget.
GenomeGenome/FitnessVector schemasThe machine-readable parent, operator, adapter, seed, package, and provenance description for a candidate.
FitnessVectorFitness vectorsA multidimensional score record covering utility, cost, latency, memory, local privacy, novelty, and human benefit.
Digital Four FsDigital Four FsFeed, Fork, Fight, and Flee: resource intake, variation, selection, and retirement/no-op.
Browser-local model labBrowser-local workbenchA local-first learning environment for inspecting model packages, adapters, diagnostics, and release evidence.
TinyRustLMTinyRustLM runtimeA Rust/WASM-oriented local runtime direction using .slm packages, quantized tensors, adapter deltas, and diagnostics.
Model mergingModel merging upsideA breeding operator that combines compatible models, task vectors, or adapters into one descendant.

How to use this page

Use this catalog when writing new guides, tools, diagrams, or discovery files. Each new term should either reuse an existing entity or add one canonical route. Avoid creating three pages that appear to own the same concept.

Machine-readable companion

The generated JSON companion lives at:

/assets/data/entity-catalog.json

It is public discovery metadata. The human page remains the primary source.

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.