Measured by one node on hardware we do not own, and signed by each of them. What machines here actually proved — never what the card claims.
matrix built 23 Aug 2026 · every field verified against the signature of the node that produced it, and re-verifiable by you: each signed figure carries the exact bytes the node signed (signing_payload_b64) and the signature over them, and the ed25519 public key is embedded in node_did. effective_ctx is the context length a node PROVED by recall, never the length a model card advertises
context declarednot declaredwhat the runtime reported. A node attests it was told this; nobody attests it is true.
context proved by recallnot probedthe largest size at which a machine could still find tokens planted across the whole prompt — start, middle and end, all of which had to come back.
Both numbers are needed to state a gap, and one of them is missing.
This model calls tools correctly and does not stop. A node watched it call the probe tool, then call it again, until the turn budget ran out. Chosen on “supports tools” alone, it will call a tool in production and never come back.
Capabilities, measured
✓Structured outputpassed
The ENGINE was asked to constrain decoding to a schema, and the answer conformed. This is stronger than politely asking for JSON and hoping: the grammar makes invalid output unreachable, which is what an operator actually builds on.
✗Extended thinkingprobed, and failed
The model emitted reasoning on the engine’s dedicated reasoning channel before answering. Read from that channel rather than by scanning the answer for tags, which is why models that reason are no longer reported as models that do not.
✓Tool callingpassed
The node asked the model to call a function and checked that it called the RIGHT one with a well-formed argument — not merely that it emitted a tool name.
✓Faithful to tool resultspassed
The model was handed a list through a tool and had to report every item back. Calling a tool and understanding its answer are different abilities: a model can produce a perfect call, receive nine items, and confidently report three. This is the flag that separates them.
✗Tool loop finishedprobed, and failed
Whether the conversation ENDED after the tool call, or the model kept calling until the turn budget ran out. A model that passes tool calling and fails this will call a tool in production and never come back.
✗Chained tool callsprobed, and failed
The model had to call one tool, read its answer, and call a second with a value derived from it. One call is not agentic work — real specialist jobs are sequences, and a model that never takes the second step looks, from outside, exactly like a specialist silently doing nothing.
✓Counts in imagespassed
Shown a row of shapes and asked how many. Reading rendered text and grasping a scene are different abilities, and a model can do the first with no spatial understanding at all — which is what charts, shelf photographs and document layout actually need.
✗Multiple images at onceprobed, and failed
Given two images and asked to compare them. Many engines and models accept one image per turn and silently drop the rest, which turns a comparison into a confident answer about half the evidence.
✓Visionpassed
A four-digit code was rendered into an image and the model had to read it back. A model that cannot see cannot guess four digits, and a model that can has no reason to fail — so this passes and fails for the right reason, which describing a picture never did.
✗Audioprobed, and failed
Given audio and asked to transcribe it.
✓faithful_tool_resultpassed
signed by this network
What machines here proved
best throughput6.45 tok/s
machines that measured it1
samples behind those numbers1
regions it was proved in1
Every line traces to a node signature.
from the public record · unsigned
What the runtime says about it
No runtime metadata was attested for this model.The only unsigned block on this page. We attest we read these from the runtime — not that they are true. Nobody signs a model card.