Attention. The reasoning architecture inside every Griffin model.
Griffin runs a long-context reasoning architecture: sliding-window plus landmark attention, a security-augmented tokeniser and structured trace output. It is the reason the lineup is fast where it needs to be and deep where it has to be.
Four pieces that make it what it is.
Sliding-window + landmark attention
Local attention over a windowed token range with sparse global landmarks. Lets Griffin reason over long call graphs without quadratic blow-up. Latency stays bounded; the window slides where the reasoning needs it.
Security-augmented tokeniser
Adds ~28,000 tokens covering CWE/CVE IDs, taint operators, package coordinates (purl format), and attack-pattern shorthand. Each is a single token instead of 4–8 BPE pieces, which keeps the security-relevant context dense.
Structured trace output
Every response is emitted as HYPOTHESIS / CITED PATH / DISPROOF / PROPOSED PATCH. The trace is the auditability story — every finding ships with the reasoning the model walked and the refutation it tried.
Four design choices a generic transformer doesn't make.
Tokeniser priors for security
Off-the-shelf tokenisers fragment CVE IDs, purls, and CWE numbers into character soup. Griffin treats them as single tokens, which preserves their semantic role inside long-context reasoning.
Long-context retrieval gates
Before attention runs, a retrieval gate pre-ranks call-graph chunks by relevance. The model only spends compute on the chunks that might matter. Time-to-first-token drops materially on long contexts.
Reasoning trace as a first-class output
Chain-of-thought in generic models is a side effect. In Griffin it is the output contract — structured, fielded, and consumable downstream by the disproof head and the auto-fix pipeline.
Adversarial disproof decoder head
A second decoder head tries to refute whatever the main head proposed. Only candidates that survive disproof reach your queue. This is how Griffin keeps false-positive rates low at production scale.
Griffin runs the attention stack.
Eagle and Lion use simpler dense architectures because their workloads don't need the long-context machinery.
Griffin (750B)
Griffin attention across its 1.1M-token context window: multi-hop cross-package exploit hypothesis, repo-wide audits and agentic disclosure workflows.
Numbers that justify the architecture choices.
Self-healing security runs on Safeguard.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.