Requesting stage-1 identity registration for 4 model-port candidates
Per docs/MODEL_PORTS_TRACK_PLAN.md's two-stage process, this is a
registration ask only -- no credit claimed here, and I understand this
review/approval PR (if you make one) earns no credit itself.
All 4 are genuinely distinct llama.cpp-et execution families (not seed
families, not size/quant variants of anything already registered), pinned to
an exact upstream commit (not a floating main), ungated, and permissively
licensed. Each has a working recipe with local sysemu verification (full ET
offload, correct param count, clean compute graph) already on our open PRs.
| Candidate model |
Execution family |
Upstream repo |
Pinned revision |
License |
falcon7b |
falcon |
tiiuae/falcon-7b |
ec89142b67d748a1865ea4451372db8313ada0d8 |
Apache-2.0 |
pythia410m |
gptneox |
EleutherAI/pythia-410m |
9879c9b5f8bea9051dcb0e68dff21493d67e9d4f |
Apache-2.0 |
bloom560m |
bloom |
bigscience/bloom-560m |
ac2ae5fab2ce3f9f40dc79b5ca9f637430d24971 |
BigScience RAIL-1.0 |
xverse7b |
xverse |
xverse/XVERSE-7B-Chat |
60acc8c453c067b54df88be98bfdf60585ab5441 |
Apache-2.0 |
Recipes with the full provenance/conversion/verification detail for each are
already on open PRs:
I know stage 1 also needs a reviewed host oracle/validation contract per new
family, not just the identity entry -- happy to draft a PPL-based contract for
each (same shape as the existing llama32_1b/smolvlm_500m contracts, since
all 4 are text-only causal LMs) for your review, if that's useful, rather than
you writing it from scratch. Let me know and I'll open that as its own PR.
Two more candidates exist (mpt7b, arch mpt/ALiBi; cohere2_7b, arch
cohere2/sliding-window) but both upstream repos are gated
(mosaicml/mpt-7b 401s the public API; CohereLabs/c4ai-command-r7b-12-2024
is gated: auto and CC-BY-NC-4.0) -- flagging honestly rather than omitting,
but leading with the 4 above since they're frictionless to reproduce.
Requesting stage-1 identity registration for 4 model-port candidates
Per
docs/MODEL_PORTS_TRACK_PLAN.md's two-stage process, this is aregistration ask only -- no credit claimed here, and I understand this
review/approval PR (if you make one) earns no credit itself.
All 4 are genuinely distinct
llama.cpp-etexecution families (not seedfamilies, not size/quant variants of anything already registered), pinned to
an exact upstream commit (not a floating
main), ungated, and permissivelylicensed. Each has a working recipe with local sysemu verification (full ET
offload, correct param count, clean compute graph) already on our open PRs.
falcon7bfalcontiiuae/falcon-7bec89142b67d748a1865ea4451372db8313ada0d8pythia410mgptneoxEleutherAI/pythia-410m9879c9b5f8bea9051dcb0e68dff21493d67e9d4fbloom560mbloombigscience/bloom-560mac2ae5fab2ce3f9f40dc79b5ca9f637430d24971xverse7bxversexverse/XVERSE-7B-Chat60acc8c453c067b54df88be98bfdf60585ab5441Recipes with the full provenance/conversion/verification detail for each are
already on open PRs:
ported_models/llama_cpp_et/falcon7b_recipe.md)exists for either; recipes document a real upstream
convert_hf_to_gguf.pybug found+fixed along the way)
ported_models/llama_cpp_et/xverse7b_recipe.md)I know stage 1 also needs a reviewed host oracle/validation contract per new
family, not just the identity entry -- happy to draft a PPL-based contract for
each (same shape as the existing
llama32_1b/smolvlm_500mcontracts, sinceall 4 are text-only causal LMs) for your review, if that's useful, rather than
you writing it from scratch. Let me know and I'll open that as its own PR.
Two more candidates exist (
mpt7b, archmpt/ALiBi;cohere2_7b, archcohere2/sliding-window) but both upstream repos are gated(
mosaicml/mpt-7b401s the public API;CohereLabs/c4ai-command-r7b-12-2024is
gated: autoand CC-BY-NC-4.0) -- flagging honestly rather than omitting,but leading with the 4 above since they're frictionless to reproduce.