Skip to content

docs(spec): the Flint port — CPU and GGUF arms (MODEL-TEXT-FLINT) - #3503

Merged
lu-zero merged 1 commit into
localai-org:mainfrom
lu-zero:row/MODEL-TEXT-FLINT
Oct 23, 2026
Merged

lu-zero merged 1 commit into
localai-org:mainfrom
lu-zero:row/MODEL-TEXT-FLINT

Conversation

@lu-zero

@lu-zero lu-zero commented Oct 22, 2026

Copy link
Copy Markdown
Collaborator

The row spec declaring MODEL-TEXT-FLINT (RecursiveSI/flint, FlintForCausalLM, published 2026-10-21): the CPU and GGUF arms of a 49-layer hybrid-attention MoE with per-head attention sinks, an ungated shared expert, sigmoid routing and a no-RoPE full-attention pattern.

Spec-first, per the row contract: this PR carries the spec and the issue only — no product code. The first wave it licenses is in the spec's Design section (the llama-cpp-flint oracle record at PR ggml-org/llama.cpp#30928's head, the model TU, and the flint GGUF loader row), with the Tenstorrent arm as a separate later row.

FOLLOWING_AGENTS_PROTOCOL

Following-Agents-Protocol: true
AI-Assisted: true
Assisted-by: AGENT:zai/glm-5.3-flash [maki]

Row declared with this spec. Scope, upstream anchors, design, risks, gates
and owed items are in the spec; the issue records the same first wave.

The reason this row exists now: the quantized artifacts are on disk and
sha256-verified, llama.cpp's only flint support is an open PR from the model
author (ggml-org/llama.cpp#30928, head 1b44e30775dcb2f93952116b05f89e5bd797f
b00), vLLM has no flint code, and the peer (mistral.rs) has started a Flint
implementation — so the architecture has a reference implementation to gate
against and a second implementation to cross-check.

FOLLOWING_AGENTS_PROTOCOL

Following-Agents-Protocol: true
AI-Assisted: true
Assisted-by: AGENT:zai/glm-5.3-flash [maki]
@lu-zero
lu-zero merged commit 11d0b3a into localai-org:main Oct 23, 2026
24 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant