🐕 The Breed Registry
Model selection as breeding selection. In the working dog paradigm, choosing the right breed is the most important decision you'll make. This registry provides structured guidance on which base model to use for which task.
Why a Breed Registry?
A working dog isn't a pet — it's bred for a purpose. Border collies herd. Labs retrieve. German shepherds protect. Each breed has instincts, temperaments, and physical traits honed over generations of selective breeding.
Foundation models are the same. GPT-4 is a generalist — like a German shepherd that can do everything. Llama-3 is an open-lineage working dog you can train yourself. Mistral is a lean, efficient breed from European lines.
Choosing the wrong breed for the job wastes resources and produces poor results. This registry exists to prevent that.
What's Inside
registry/ — Breed Assessments
Each model is assessed like a dog breed at a confirmation show, but for working aptitude instead of conformation:
| Field | Dog Analogy | Model Meaning |
|---|---|---|
lineage |
Pedigree / bloodline | Model family and training lineage |
breed_group |
AKC group (Herding, Sporting, etc.) | Task category (General Purpose, Working, etc.) |
temperament |
Breed temperament traits | Behavioral characteristics (careful, verbose, etc.) |
working_aptitude |
Instinct tests & working trials | Task-specific capability scores (0-10) |
cost_profile |
Feed & maintenance cost | API cost per token |
speed_profile |
Speed/agility rating | Inference latency |
trainability |
How well it takes to training | Fine-tune response quality |
recommended_for |
Best-suited jobs | Tasks where this model excels |
not_recommended_for |
Jobs it's wrong for | Tasks where this model struggles |
fence_compatibility |
How well it respects boundaries | Conservation bytecode compliance |
src/breed_registry/ — Python API
from breed_registry import select_breed, compare_breeds, assess_aptitude
# Find the best breed for a task
recommendations = select_breed("code_generation")
# Compare two breeds head-to-head
report = compare_breeds("gpt-4", "llama-3")
# Check a specific model's aptitude for a task
score = assess_aptitude("mistral", "analysis")
Registered Breeds
| Breed | Group | Cost | Speed | Best For |
|---|---|---|---|---|
| GPT-4 | General Purpose | High | Moderate | Complex reasoning, code generation |
| [Claude-3](registry/claude-3.json | General Purpose | High | Moderate | Analysis, careful reasoning |
| Llama-3 | Open Lineage | Free | Fast | Local deployment, fine-tuning |
| GLM | General Purpose | Low | Fast | Multilingual, efficient inference |
| Mistral | Working | Low | Fast | Efficient European-lineage tasks |
Selection Philosophy
1. Match the Breed to the Job
Don't use a high-cost generalist for simple classification. Don't use a lightweight model for complex multi-step reasoning. Match instincts to tasks.
2. Consider the Lineage
Model families carry traits across generations. Fine-tunes inherit strengths and weaknesses. Know the pedigree before you commit.
3. Respect the Fence
Conservation compliance — how well a model respects guardrails and bytecode fences — is non-negotiable for production work. A model that won't respect boundaries is a liability.
4. Trainability Matters
Some breeds take to fine-tuning naturally. Others resist. If you need to specialize, choose a breed known for trainability.
Adding a Breed
To register a new model:
- Create
registry/<model-name>.jsonfollowing the assessment schema - Add an entry to
registry/index.json - Submit a pull request
Assess honestly. Overrating a model's working aptitude helps no one — least of all the teams who deploy it.
License
MIT
Part of the Working Animal Architecture — foundation models as working animals, not pets.
Metadata
Release files for breed-registry 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| breed_registry-1.0.2.tar.gz | 11.4 kB | Without provenance | Details for breed_registry-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| breed_registry-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for breed_registry-1.0.2-py3-none-any.whl |
Total release size: 20.2 kB
Release files / breed_registry-1.0.2.tar.gz
| Download URL | breed_registry-1.0.2.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e2a82ccc4a4e756281b320f6992043a6999105dbc239d5d898ead69553455a5
|
|
BLAKE2b-256 checksum How to use checksums |
d3af7da2b908ed46859a202553d5483fdd1367921b6f58a3877b14317ca77284
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / breed_registry-1.0.2-py3-none-any.whl
| Download URL | breed_registry-1.0.2-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be712d7545336e94365c0d6823dc3a6c2e4f0316378d060160609f9b5d82dbab
|
|
BLAKE2b-256 checksum How to use checksums |
9bd80e7a5acc4b27c277dfe6a43127a2e559ad3d92effa09aed8905659e18bed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for breed-registry 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.