Hy-Memory-30B-A3B vs Qwen3.5-397B-A17B

Hy-Memory-30B-A3B 68

Model card 8, Intended use (the write path of Mem0, MemOS and Hy-Memory), parameters (30B, about 3B active) and languages (English and Chinese, in the metadata) are there. Training data 5, A general description of the two training stages inside the harnesses, with no datasets, sizes or cut-off. Last change 20, the last commit, on 16 October 2026, added the licence and the card, 25 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (16 to 30 October 2026), 3 have a reply from a tencent organisation member. Version policy 5, A first release, with nothing replaced. File health 10, Config, tokenizer and template agree on the architecture, the context and the thinking levels. 8 + 5 + 20 + 20 + 5 + 10 = 68.

Qwen3.5-397B-A17B 34

The card covers five of the seven items and misses limitations and a cut-off (14). Training data is a general description without a cut-off (5). The files last changed on 24 April 2026, 192 days before this check, past the 180-day band and within a year (5), and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. Alibaba answered none of the 40 most recent questions and reports, recounted on 2 November (0), and GitHub issues couldn't be counted. It's a first release at this size (5), and two template reports and a template fix still wait unanswered (5). 14 + 5 + 5 + 0 + 5 + 5 = 34.

Hy-Memory-30B-A3B 85

Memory 25, Tencent's own Q4_K_M GGUF is 18.24 GB, and 18.24 GB × 1.2 = 21.9 GB, which fits 24 GB but not 16 GB. Its Q3_K_M file and the two files with experts at 1 or 2 bits are below 4-bit precision and don't count. Runtimes 20, hy_v3 model code in released vLLM (HYV3ForCausalLM in the v0.33.0 registry), SGLang v0.5.23 (hunyuan_v3.py), Transformers v5.22.2 and llama.cpp b12242, 5 each. Builds 15, Tencent publishes an FP8 repository and a GGUF repository with Q4_K_M, Q6_K and Q8_0 files in its own organisation, so quantised builds at two precisions or more. Terms 15, Apache 2.0, with only a preamble naming Tencent as copyright holder above the licence text. Download 10, gated is false for the main, FP8 and GGUF repositories on 10 November 2026, so the files download with no account or terms to accept. Hosted 0, Hugging Face lists no inference provider for the model (an empty provider mapping on 10 November 2026), and the card names no API. 25 + 20 + 15 + 15 + 10 + 0 = 85.

Qwen3.5-397B-A17B 70

Memory scores 0, since even the smallest 4-bit build, LM Studio's MLX 4-bit at 223.9 GB, needs about 269 GB with a fifth added, and Alibaba's own GPTQ-Int4 about 283 GB. Runtimes reach the 25 cap on released llama.cpp, vLLM, SGLang and Transformers and LM Studio's catalogue, though Ollama has no local build. Alibaba's FP8 and GPTQ-Int4 builds give builds 15. Apache 2.0 with nothing added gives terms 15, the ungated repositories give download 10, and Alibaba's Model Studio plus five live providers on Hugging Face give hosted too its 5.

Hy-Memory-30B-A3B 60

File safety 25, 51 safetensors shards and no pickle or Python files. Provenance 15, files in the tencent organisation that the card's own resource list links to (10), with a SHA-256 listed for all 53 large files (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, no prompt-injection guidance, instruction hierarchy, account of trained refusals or general cautions on the card. Licence risk 15, Apache 2.0 with no use policy, no field-of-use limit, no threshold and no clause letting Tencent change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide with published reward rules, as the Hy3 listing records (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Qwen3.5-397B-A17B 55

Safetensors only with no repository code run on load or to build prompts gives file safety 25, and files in the Qwen organisation the publisher's GitHub links to, each hashed on the Hub, give provenance 15. Plain Apache 2.0 keeps licence risk at 15. Safety evaluation, agent guidance and a security programme score 0. The card has no safety results (its SecCodeBench row is a coding capability), no cautions, and no reporting route was found. The Qwen3.5 blog and Alibaba's security response centre couldn't be read, so both are scored as absent and left open.

Hy-Memory-30B-A3B 65

Chat template 20, chat_template.jinja in the repository. Tool-calling format 10, the card doesn't mention tools. Trained tool calling 10, the template can render tool calls, but the card presents the model as a memory writer that returns memories as text or JSON and says nothing of calling tools. Structured output 5, the card's quickstart asks for a JSON object with a memories list in the system prompt and shows nothing else, no response_format and no schema, so JSON output is shown by example without a documented way to constrain it. Reasoning control 10, the card passes reasoning_effort as no_think per request through chat_template_kwargs, and the template takes high, low or no_think. Context 10, 262,144 tokens native (max_position_embeddings in config.json). 20 + 10 + 10 + 5 + 10 + 10 = 65.

Qwen3.5-397B-A17B 70

The template ships in the repository (20) and renders several tool calls per turn for a model trained for tool use (20). Tool-calling format gets 10, because the card names the qwen3_coder parser but leaves the declaration and call format to the template. Thinking turns off per request and comes back in think tags split by the qwen3 parser (10), and 262,144 tokens is native (10). Structured output scores 0, as nothing documents JSON output for the model.