Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions docs/arch-gaps.md
Original file line number Diff line number Diff line change
Expand Up @@ -1224,3 +1224,33 @@ The one `!! UNCOVERED` line of the 2026-11-14 watcher run. Read from the repo's
not alerted (`"watch": "report"`), so the daily watcher prints `. REVIEWED` instead of `!! UNCOVERED` and
does not exit 1 on it. If a backend starts accepting the class, record why as `mapped_ok` in
`registry/significant.json` rather than deleting this entry.

## `megatron_gpt_moe` — Megatron-LM GPT-MoE checkpoints

* **Class / model_type**: `MegatronGPTMoeForCausalLM` / `megatron_gpt_moe`; example
`nagohachi/tiny-lm-v3-japanese-1.5b-a500m-sft`.
* **Evidence**: the repo's HF tags carry `megatron_gpt_moe` and `custom_code`
(checked 2026-11-17) — the modeling code ships in the repository rather than in
transformers, which is what the census calls `REMOTE-CODE`.
* **Why an alias is wrong**: this is a **training-framework checkpoint format**,
not a serving topology. A gguf conversion of one lands on whichever
architecture its exporter targets, so there is no single engine arch to map it
to, and treating it as an alias of `qwen*moe` / `llama` / `deepseek2` would
serve the model with the wrong tensor names — the failure mode that produces a
load error at best and wrong numbers at worst.
* **Real support needs**: an exporter (Megatron → gguf) and then whichever arch
it emits; the engine side would be that arch's path, not this class.

## `rusmind_ai` — RusMind AI (from-scratch)

* **Class / model_type**: `RusMindAIForCausalLM` / `rusmind_ai`; example
`DICPlay/RusMind-Zernyshko-2.0.1`.
* **Evidence**: the repo's HF tags carry `rusmind_ai`, `from-scratch` and
`custom_code` (checked 2026-11-17). The `from-scratch` tag is the load-bearing
one: it says this is not a finetune of a known family under a new name, which
is the case where a mapping would otherwise be plausible.
* **Why an alias is wrong**: the class string of a renamed finetune is not
evidence of the underlying architecture, and here the repository says it is a
new architecture. Mapping on the name would be guessing at the tensor layout.
* **Real support needs**: the architecture itself (attention/FFN/embedding
layout) plus a converter; nothing to map until that exists.
4 changes: 2 additions & 2 deletions registry/census.json
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@
"declined": "a human reviewed the class and deliberately did not map it (registry/significant.json, `watch: \"report\"`). Counted separately and excluded from top_unmapped: it is a recorded decision, not work remaining. The denominator is unchanged -- declined models are still `with_architecture`",
"with_architecture": "models whose HF card names an architecture this census can look up; models with no architecture are excluded from every percentage above"
},
"declined_models": 434,
"declined_architectures": 21,
"declined_models": 442,
"declined_architectures": 23,
"models": 438457,
"with_architecture": 345360,
"architectures_seen": 3071,
Expand Down
Loading
Loading