Hy-Memory-30B-A3B vs Swift 1.5 Qwen3.8-27B

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.

Swift 1.5 Qwen3.8-27B 43

Model card 8 of 20, intended use, parameters and context only. Training data 5, a general description with no cut-off. Last change 20, UkisAI's own ONNX builds of the model took a new card and licence on 8 October, 26 days ago (the main repository's last commit is the 3 October README update). Responsiveness 0, UkisAI answered none of 8 discussions. Version policy 5, Swift 1.0 stays in its own repository without a note. File health 5, reports of a broken model wait without a reply and the card's metadata claims a gate that doesn't exist.

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.

Swift 1.5 Qwen3.8-27B 50

File safety 25, safetensors only and nothing from the repository runs. Provenance 15, the files are in the account UkisAI's site links to, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 10, a revenue threshold. Security programme 0, no way to report a flaw was found.

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.

Swift 1.5 Qwen3.8-27B 80

Memory 25 of 30, UkisAI's 4-bit MLX build is 15.9 GB and its 4-bit GGUF with the vision projector 16.4 GB, both under 20 GB with a fifth added, which fits 24 GB. Runtimes 20, the architecture is Qwen3.8-27B's, which released llama.cpp, vLLM, SGLang and Transformers run, while Ollama's entry is the base's. Builds 15, GGUF, INT4, NVFP4, FP8 and MLX builds from UkisAI. Terms 10, a custom licence that is free for commercial use below US$1M revenue. Download 10, not gated. Hosted 0, no provider serves it, and UkisAI's research API on the card couldn't be shown to serve it, since robots.txt disallows calling it.

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.

Swift 1.5 Qwen3.8-27B 60

Chat template 20, the base's Jinja file. Tool-calling format 10 of 25, the format is only in the template and the parser only in serving commands. Trained tool calling 20, several calls a turn and agentic post-training. Structured output 0, not documented. Reasoning control 0, the card mentions reasoning_effort but not how to set it, turn thinking off or read the reasoning. Context 10, 262,144 tokens native.