How to read this model, and what it shows about an AI model that reasons, trains and operates on Axiom Vertex.
What this model shows
The model follows one question through an AI model, from the validated records that the model reads to the answer that it writes, and sets the result beside the same question over retrieved context. It lets a technical reader see, step by step, where Axiom Vertex acts and where the AI model's own computation begins.
How to use it
- Example. Choose a scenario. General Purpose, Agentic, Finance, Healthcare and Robotics each use real validated records and a real run of the model.
- Context. Drift-free context is built from the validated records that Axiom Vertex holds at fixed coordinates, so the same validated bytes reach the model on every run. Retrieved context is assembled by retrieval, as in retrieval-augmented generation, and can differ between runs.
- Retrieval run. This control appears for retrieved context. The same question is asked three times, and each run shows the records that retrieval returned that time and the answer that the model wrote.
- Stages. Twelve stages follow the question from the validated records to the verified results. Back, Play and Next move through them, and Details explains the stage on screen.
- Temperature and Sampling. These controls act on the next-token probabilities, which the next section explains.
What is being sampled
An AI model that writes text produces one token at a time. At each step it holds a score, a logit, for every token in its vocabulary. Softmax turns the scores into probabilities that add up to 100 percent, and sampling then chooses the next token from those probabilities. The step repeats until the answer is complete.
The controls shape the choice. Temperature divides the scores before softmax. Below 1 the most probable tokens gain weight and the choice becomes more predictable, and above 1 the probabilities spread out. Top-k keeps only the k most probable tokens, so a value of 5 keeps five candidates. Top-p keeps the fewest tokens whose probabilities add up to at least p, so a value of 0.9 keeps the tokens that together hold 90 percent. In both cases the kept probabilities are scaled to add up to 100 percent again, and the next token is drawn from them.
In this model the answer is produced by greedy decoding, which always takes the most probable token, so the controls change the display on stage 9 and not the answer. Sampling is the AI model's own setting, and on the standard request path the platform forwards it as sent.
What to look for
Integrity. Every record and the question is validated at its ingest gateway before the AI model reads it, and each receives a validation proof (stage 1). The context hash identifies the exact bytes that the model reads. With drift-free context the context hash is identical from run to run, and in this model's runs every internal value and the answer are identical too (stages 6 to 11). With retrieved context the hash changes when the records change, and the answer can change with it. The platform guarantees the context, and the quality of the answer remains the model's.
Operations. The customer hosts and executes the AI model on the customer's own infrastructure, and the platform validates the data around it. Context assembly is a separate query that the AI application sends (stage 5), so the model, its serving stack and its sampling settings stay as they are. The same mechanism serves AI models that use tokens and AI models that do not, and the AI agents built on them (stage 12). The organization's data stays in its own storage, and each Virtual Organization is an isolated tenant with its own compute fabric, ledger and storage.
Performance and scale. At scale the work is divided by sector. Six reasoning bridges, one for each sector of an organization's data, reason independently, and the runners within a bridge execute in parallel; a query across the organization is recomposed from the results of the bridges into one (stage 4). The platform's verification tests confirm that runner capacity holds exactly under concurrent load, that the full reasoning pipeline proposes the expected runners with a verifying proof at every hyperdimensional tier, and that the reasoning bridges route each query to the correct runner, identically on repeat (stage 12). The check on a model's internal state costs the same whether the model has 8 billion or 405 billion parameters, so the verification layer does not become more expensive as an organization adopts larger models.
Reasoning, training and operating at scale
Reasoning. A query is resolved within the sector in which its coordinate falls, and a query across the organization is recomposed from the bridges that contributed. The work spreads across the bridges as data arrives.
Training. Training data is validated before it is used. The organization trains its model on its own infrastructure, and the resulting checkpoint is forged, validated and recorded with an attestation that binds the trained model to its data and its training record. The model that is trained, the data that trained it and the context that it later reads are each identified by proofs that a third party can check with the owner's authorization.
Operation. Each Virtual Organization operates on its own compute fabric, so organizations scale independently of one another. Within an organization, capacity grows as data arrives and the reasoning bridges divide the work by sector. The practical limits are the organization's own storage and compute capacity.
About the model shown
The model runs a small open AI model, Qwen2.5-0.5B-Instruct, so that every internal value can be shown. The mechanisms are the same for AI models of any size, and the statements about scale rest on the platform's verification tests.
Sources
Top-k sampling follows Fan, Lewis and Dauphin (2018), and top-p sampling follows Holtzman and others (2020). The attention computation follows Vaswani and others (2017). The statements about scale follow the platform's verification tests.