Registry purpose
A model-breeding registry records not only the model artifact, but also the recipe that produced it. This is essential for positive compounding because future builders need to know which parent, merge ratio, pruning policy, evaluation set, and reviewer produced each child.
Registry record
| Field | Example |
|---|---|
artifact_id | adapter-csharp-review-v003 |
base_family | qwen2-0.5b-instruct |
parents | style-v002, bug-review-v004 |
operator | ties_adapter_merge |
recipe_hash | Hash of merge config. |
evaluation_card | Path to benchmark evidence. |
status | candidate, canary, active, retired. |
FUNCTION register_merge_child(child, recipe, evaluation)
record = {
artifact_id: child.id,
base_family: child.base_family,
parents: recipe.parents,
operator: recipe.operator,
recipe_hash: hash(recipe),
evaluation_card: evaluation.path,
status: "candidate"
}
append_jsonl("registry/model-artifacts.jsonl", record)
RETURN record
END FUNCTIONPositive outcome
The registry turns model breeding into a cumulative engineering discipline instead of an ad hoc folder full of weights.
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.
Model merging and adaptersModel Merging: Definitions, Taxonomy, Algorithms, Tooling, and Production Pipeline DesignEmerging practice · 35.7 KB
Model merging and adaptersTiny-LLM Adapters and LoRA: Breeding Operators, Compatibility, Evaluation, and PromotionEmerging implementation practice · 15.3 KB
Browser and edge runtimeOn-Device Tiny Language Models and Model Breeding StrategiesEmerging implementation practice · 33.9 KB