Status: unevaluated and disabled
Per MoE-Foundry's rule an exported specialist starts quality_status: unevaluated, enabled: false. A structural export proves tensor integrity, not retained capability. This checkpoint is published so that slim-eval (slim/eval: run, redteam, regression, verdict) can measure it against the parent on the frozen ruOS test split; until that verdict is recorded here it must not be routed to. The full parent remains the fallback.
Parent
Table | |
|---|
| repo | Qwen/Qwen3-30B-A3B-Instruct-2507 |
| revision | 0d7cf23991f47feeb3a57ecb4c9cee8ea4a17bfe |
| licence | Apache-2.0 |
| MoE-Foundry parent_id | 44c2b6971fe6979409ac72586db5fa4abfd73746afc52607368a59740848149d |
| experts per routed layer (parent → this) | 128 → 64 |
| routed layers | 48 |
| token top-k (unchanged) | 8 |
Calibration
Domain ruos-swarm: 64 rows (9 from the val split, 55 topped up from train; the test split is never used for calibration), ~22508 tokens, families {"swarm":64}, licences {"project-owned":64}. Calibration file sha256 94a5527b141269ab5078a14e3d129b387aa69412c65334160715fd9a58dbfef5. Texts are the ChatML prompt plus the reference answer.
Router traces: 412 tasks, 148144 tokens, 7110912 rows on NVIDIA A100-SXM4-80GB (bfloat16, transformers 4.51.3); trace sha256 7aabb05cbf715156437393fc5a5b0d756951ecee35eb4542a06fc812f11f9403.
Selection method: mass (accumulated routing probability per expert per layer) — a usage proxy, not causal importance.
Receipt
Table | |
|---|
| specialist_id | cb102eec27bec133996063ed2999dbcd41f918a1f17fa212eac3271244fdeb93 |
| checkpoint_id | 66ea9f3a54b1e35812c8e8f429de84261e45670c66599e81f508f3a893f65eb4 |
| mask_sha256 | 8edf60090f87097f9816e9e39fee82ef4c36ab24f3154867b155f89254de6210 |
| parent_id | 44c2b6971fe6979409ac72586db5fa4abfd73746afc52607368a59740848149d |
| input tensor bytes | 61064245248 |
| output tensor bytes | 32060633088 |
separator_receipt.json in this repo is the full MoE-Foundry receipt including the per-layer expert mask.
Files
Table with columns: path, bytes, sha256| path | bytes | sha256 |
|---|
| LICENSE | 11343 | 05cab46843576551502bfdf712f84e93e6e9590d9997306ed4f6635ef82811d9 |
| SHA256SUMS | 737 | 7c0be9e4ae99b8d45f4b28a296f00d577cd05b645fd7a0684d2733abd54e0610 |
| config.json | 963 | f0bf60e7da89b14b5763344441e4f60eccda09f62c0111c5f178283c5f3d81ec |
| generation_config.json | 239 | 19d306dd769db12a9d710b44cf7f83b635efbe5166b84fb4358a08fb7d88bb53 |
| merges.txt | 1671839 | 599bab54075088774b1733fde865d5bd747cbcc7a547c5bc12610e874e26f5e3 |
|
Run
vllm serve ruvnet/ruos-foundry-swarm-qwen3-30b-a3b-e64 --max-model-len 8192
Loads with transformers as a standard qwen3_moe checkpoint (single safetensors file, num_experts reduced in config.json).
Limitations
- Unevaluated: no capability, memory or latency claim is made here.
- Retained experts were chosen by routing mass on ruOS calibration prompts; requests outside that domain should go to the parent.
- Memory: fewer experts means a smaller checkpoint; loading several specialists next to the parent can use more total memory than the parent alone.
Provenance
- MoE-Foundry
6677a25 (moe-separator inspect → profile_hf → select → export → mixture)
- run
foundry-20260907T172935Z-qwen3-30b-a3b on a single vast.ai GPU; ruos-desktop slim/foundry + slim/scripts/foundry-e2e.sh
- authorisation: rUv, "implement this using ruvnet/MoE-Foundry using vast.ai in a worktree, implement e2e and push models to repo"