# Vraelis documentation > Vraelis develops cybersecurity software for AI in defense, critical infrastructure and autonomous systems. These docs cover Vraelis, its one product direction (Vraelis Contour, model release security from approval to reported runtime state), its research, and earlier implementation references kept as history. Vraelis Contour is not for public use: it is built for release, platform and security engineers at suppliers and system integrators. Every page labels each claim as working in the experiment, measured, proposed, hypothesis or not claimed. - [Docs home](https://docs.vraelis.com/): Get started with Vraelis. ## Vraelis What Vraelis is, how to read these docs, development status, release notes and a glossary. - [Introduction to Vraelis](https://docs.vraelis.com/introduction) ([Markdown](https://docs.vraelis.com/md/introduction.md)): What Vraelis is, the research it works on, its one product direction, and where these docs fit. - [How to read these docs](https://docs.vraelis.com/reading-the-docs) ([Markdown](https://docs.vraelis.com/md/reading-the-docs.md)): The five kinds of statement every page keeps apart, what the pictures and code are, and the ways to read a page: search, Ask AI and Markdown. - [Development status](https://docs.vraelis.com/status) ([Markdown](https://docs.vraelis.com/md/status.md)): Where Vraelis Contour stands: what works in the experiment, what is being built, and what Vraelis does not claim. - [Release notes](https://docs.vraelis.com/release-notes) ([Markdown](https://docs.vraelis.com/md/release-notes.md)): Dated changes to Vraelis and Vraelis Contour, newest first. - [Glossary](https://docs.vraelis.com/glossary) ([Markdown](https://docs.vraelis.com/md/glossary.md)): The words these docs use, each with what it means and where it stands. ## Products Vraelis Contour, the one product direction: how it works today, what the experiment records, and where it stops. - [Products](https://docs.vraelis.com/products) ([Markdown](https://docs.vraelis.com/md/products.md)): Vraelis has one product direction, Vraelis Contour. There are no other Vraelis products. - [Vraelis Contour overview](https://docs.vraelis.com/contour) ([Markdown](https://docs.vraelis.com/md/contour.md)): What Vraelis Contour is, where it stands today, and the five-step release workflow it is built around. - [Release identity](https://docs.vraelis.com/release-identity) ([Markdown](https://docs.vraelis.com/md/release-identity.md)): How a release is named as one exact thing: the model, configuration, release and receipt digests, and the preprocessing identity that is still proposed. - [Approval binding](https://docs.vraelis.com/approval-binding) ([Markdown](https://docs.vraelis.com/md/approval-binding.md)): How an approval names the exact release, its destination and the runtime policy, and what the recorded trace keeps of it. - [Runtime integration and policy](https://docs.vraelis.com/runtime-integration) ([Markdown](https://docs.vraelis.com/md/runtime-integration.md)): The one runtime the experiment supports, the signed runtime policy it enforces, and what is recorded but not bound by that policy. - [Comparing approved and reported](https://docs.vraelis.com/comparing-approved-and-reported) ([Markdown](https://docs.vraelis.com/md/comparing-approved-and-reported.md)): How Vraelis Contour puts the approved release beside the identity the runtime reports loading, field by field, and how to read the result. - [Evidence and observations](https://docs.vraelis.com/evidence-and-observations) ([Markdown](https://docs.vraelis.com/md/evidence-and-observations.md)): What an observation records, the three statuses and their reason codes, the four recorded observations, and the scope of a worker self-report. - [The evidence app](https://docs.vraelis.com/evidence-app) ([Markdown](https://docs.vraelis.com/md/evidence-app.md)): The read-only app over the recorded trace: its six screens, what opening a trace checks, and why opened files are labelled Imported, not verified. - [Limits and what is not built](https://docs.vraelis.com/limits) ([Markdown](https://docs.vraelis.com/md/limits.md)): What works in the experiment, what is being built, what Vraelis does not claim, and what the evidence does not establish. ## Research The four research areas and the guides on model releases, operating constraints and AI security evaluation. - [Research](https://docs.vraelis.com/research) ([Markdown](https://docs.vraelis.com/md/research.md)): Our work spans model integrity, adversarial threats, machine trust and security evidence. Four research workstreams, not products, and how they connect to Vraelis Contour. - [Model integrity](https://docs.vraelis.com/model-integrity) ([Markdown](https://docs.vraelis.com/md/model-integrity.md)): A research area, not a product: whether the model that runs is the model that was approved. What we study, what exists in the Vraelis Contour experiment, and what is still open. - [Adversarial threats](https://docs.vraelis.com/adversarial-threats) ([Markdown](https://docs.vraelis.com/md/adversarial-threats.md)): A research area, not a product: inputs, training data, updates and supply paths built to change what a model does. Research direction with no product claim. - [Machine trust](https://docs.vraelis.com/machine-trust) ([Markdown](https://docs.vraelis.com/md/machine-trust.md)): A research area, not a product: zero trust described as concrete boundaries. Explicit identity, limited permissions, approval tied to a change and destination, and checks at execution boundaries. - [Security evidence](https://docs.vraelis.com/security-evidence) ([Markdown](https://docs.vraelis.com/md/security-evidence.md)): A research area, not a product: records a person can read, kept in order, including what could not be confirmed. What exists in the Vraelis Contour experiment, and what is still open. - [A model release is a security decision.](https://docs.vraelis.com/model-release-security) ([Markdown](https://docs.vraelis.com/md/model-release-security.md)): For the release, platform and security engineers responsible for moving an approved model into an operational system. - [Different systems. Different security boundaries.](https://docs.vraelis.com/operating-constraints) ([Markdown](https://docs.vraelis.com/md/operating-constraints.md)): The control has to fit the environment, not just the model. - [Measure the boundary, not a broad security score.](https://docs.vraelis.com/ai-security-evaluation) ([Markdown](https://docs.vraelis.com/md/ai-security-evaluation.md)): Match the threat to a measurable test. ## Optional: earlier references (not current) The earlier browser-testing product, kept as history. Not current. - [Getting started with Vraelis](https://docs.vraelis.com/getting-started) ([Markdown](https://docs.vraelis.com/md/getting-started.md)): Earlier implementation reference. Write one sentence about your deployed app, approve the plan, and read your first decision. - [Verify, approve, run, re-check](https://docs.vraelis.com/the-loop) ([Markdown](https://docs.vraelis.com/md/the-loop.md)): Earlier implementation reference. The whole loop, in the order it happens, in each of the ways to run it. - [What you can check](https://docs.vraelis.com/what-you-can-check) ([Markdown](https://docs.vraelis.com/md/what-you-can-check.md)): Earlier implementation reference. Every kind of thing Vraelis is for, and whether it works today. - [Connect an AI assistant](https://docs.vraelis.com/ai-assistants) ([Markdown](https://docs.vraelis.com/md/ai-assistants.md)): Earlier implementation reference. Let an assistant check its change on the live app over MCP, and hand you the approval. - [The command line](https://docs.vraelis.com/cli) ([Markdown](https://docs.vraelis.com/md/cli.md)): Earlier implementation reference. Install the vraelis CLI, check a claim from a terminal, and read the decision from its exit code. - [The API](https://docs.vraelis.com/api) ([Markdown](https://docs.vraelis.com/md/api.md)): Earlier implementation reference. Submit a claim, have a person approve the plan, start the run, read the decision and re-check after a fix, over HTTP. - [Gate a release in CI](https://docs.vraelis.com/ci) ([Markdown](https://docs.vraelis.com/md/ci.md)): Earlier implementation reference. Run a check from a CI job and ship only when the decision is verified. - [Webhooks](https://docs.vraelis.com/webhooks) ([Markdown](https://docs.vraelis.com/md/webhooks.md)): Earlier implementation reference. Get a signed verification.completed event when a verification finalizes, and check its signature. - [Approving a plan](https://docs.vraelis.com/review) ([Markdown](https://docs.vraelis.com/md/review.md)): Earlier implementation reference. The one step only a person can take, and why an API key cannot. - [Run activity](https://docs.vraelis.com/run-activity) ([Markdown](https://docs.vraelis.com/md/run-activity.md)): Earlier implementation reference. What a verification did, step by step, with the evidence it captured. - [Completion](https://docs.vraelis.com/completion) ([Markdown](https://docs.vraelis.com/md/completion.md)): Earlier implementation reference. Verified, Failed, or Blocked, with the evidence behind it. - [Findings](https://docs.vraelis.com/findings) ([Markdown](https://docs.vraelis.com/md/findings.md)): Earlier implementation reference. What broke, in terms a person or a coding agent can act on. - [Repair](https://docs.vraelis.com/repair) ([Markdown](https://docs.vraelis.com/md/repair.md)): Earlier implementation reference. A repair prompt for whoever fixes it, and a re-check that proves the fix. - [Re-checks](https://docs.vraelis.com/recheck) ([Markdown](https://docs.vraelis.com/md/recheck.md)): Earlier implementation reference. Run the same approved plan again after a fix, within its limits, without a new approval. - [Systems](https://docs.vraelis.com/systems) ([Markdown](https://docs.vraelis.com/md/systems.md)): Earlier implementation reference. Every app you have connected, and how the last run on each one decided. - [Guarantees](https://docs.vraelis.com/guarantees) ([Markdown](https://docs.vraelis.com/md/guarantees.md)): Earlier implementation reference. A claim saved so it can be checked again. - [Memory](https://docs.vraelis.com/memory) ([Markdown](https://docs.vraelis.com/md/memory.md)): Earlier implementation reference. What is kept after every run, and what is not read back. - [Review recorded task reports](https://docs.vraelis.com/recorded-reports) ([Markdown](https://docs.vraelis.com/md/recorded-reports.md)): Earlier implementation reference. Compare supplied control-panel, service and device reports for one task. Inspect disagreements, missing evidence and changes to another asset.