# OneVir control evidence and deployment responsibilities Review six OneVir control topics, the evidence behind each finding, and what to verify for your release and deployment. ## Source snapshot - Published: 2026-10-07. Article updated: 2026-10-07. Source reviewed: 2026-10-07. - Author: OneQuill Research. Affiliation: OneQuill develops OneVir. - Source package: OneVir 0.2.43 (working tree; not a verified release artifact). - Base revision: `2164d6209a7f66e3c00913e430916d5595dd6c36`. - Snapshot state: Working tree with uncommitted sources. The base revision alone does not identify the reviewed files. - Snapshot captured: 2026-10-07T14:02:36Z. - Method: Documentary review of named source paths and test assertions; referenced tests were not executed for this publication. - Release applicability: Not established; request evidence for the installed release and effective configuration. This is not an independent audit, certification or deployment guarantee. The [source snapshot JSON](https://onequill.dev/assets/downloads/onevir-source-snapshot.json) records SHA-256 fingerprints for the seven named files without publishing source contents or private configuration. ## At a glance | Control and finding | Evidence status | Verify in your deployment | | --- | --- | --- | | [Security](https://onequill.dev/resources/onevir-control-evidence#security): The named test asserts rejection of conflicting credentials and handling of supported bearer and WebSocket formats. | Test source reviewed; referenced test not run | Endpoint coverage, key scopes, administrative permissions and transport security. | | [Privacy](https://onequill.dev/resources/onevir-control-evidence#privacy): Initialisation rejects an invalid saved retention policy; named history paths describe retention and image restrictions. | Implementation and API documentation reviewed | Effective retention settings and data flows through providers, caches, files, exports and backups. | | [Budgets](https://onequill.dev/resources/onevir-control-evidence#budgets): The named test asserts two admissions from eight competing attempts against a two-attempt allowance. | Test source reviewed; referenced test not run | Configured prices, settlement, incomplete streams and counters across enabled routes and nodes. | | [Reliability](https://onequill.dev/resources/onevir-control-evidence#reliability): Named source paths describe provider health states, cooldown and trial behaviour, and health-aware fallback selection. | Implementation and source documentation reviewed | Recovery times, partial streams, provider failure behaviour and restart durability. | | [Supply chain](https://onequill.dev/resources/onevir-control-evidence#supply-chain): The source manifest pins llama-cpp-sys-2 to =0.1.157; this identifies one declared dependency. | Dependency declaration reviewed | Delivered artifact digest, complete dependency inventory, model revisions and vulnerability assessment. | | [Inference](https://onequill.dev/resources/onevir-control-evidence#inference): Named sources distinguish GGUF execution on llama.cpp from exported accelerator assets. | Implementation and engine boundary reviewed | Separate inference services, patch levels, endpoint exposure, execution location and memory isolation. | ## Responsibilities: who supplies the evidence Use this division of work to plan your evaluation. It describes evidence to request and checks to assign; it does not establish contractual or legal responsibility. | Participant | Evidence to request or record | What to verify for the deployment | | --- | --- | --- | | OneQuill / OneVir implementation | Release identifiers, the relevant source snapshot, control scope, dependency declarations and available test or demonstration records. | Whether the supplied record covers the installed build and the paths being used. | | Deployment operator | Installed artifact digest, effective configuration, endpoint and permission matrix, provider and model inventory, and an accountable owner for each control. | Retention and data flows, route accounting, failure recovery, access boundaries and changes to the configuration. | | Connected provider or inference service | Service and model versions, data-handling terms and settings, patch information, endpoint exposure and service-specific test evidence. | Where each request executes and what the upstream stores, bills, retries or isolates. | Ask OneQuill for implementation and release evidence. Record your own configuration and results. Request service-specific evidence from every connected provider. A source review does not replace those deployment checks. ## Security: credential interpretation **Reviewed finding:** The named test asserts rejection of conflicting bearer and API-key credentials, normalisation of supported bearer syntax, and separate handling of WebSocket credentials. **Evidence status:** Test source reviewed. The referenced test was not run for this publication. **Verify in your deployment:** Obtain the installed version, key scopes and an endpoint and permission matrix. Check application and administrative access separately, including transport security. **Limit:** This finding covers credential interpretation. It does not establish endpoint coverage, administrative permissions or complete authentication correctness. ### Technical detail: credential test source The source snapshot identifies this test: ~~~text File: src/api/mod.rs Test: access_auth_normalizes_supported_credentials_and_rejects_ambiguity ~~~ Its assertions distinguish supported bearer syntax, matching and conflicting credentials, unsupported authentication syntax and the WebSocket credential path. These are assertions in test source, not published execution results. Product context: [OneVir capabilities](https://onevir.onequill.dev/#capabilities). Traceability: [source snapshot and file fingerprints](https://onequill.dev/assets/downloads/onevir-source-snapshot.json). ## Privacy: retention and saved history **Reviewed finding:** The named initialisation path refuses to start with an invalid saved retention policy. Named history API paths describe restrictions on saved conversations and images. **Evidence status:** Implementation and API documentation reviewed. Retention and deletion were not demonstrated for a deployment. **Verify in your deployment:** Record the effective retention settings and trace data through providers, caches, files, exports and backups. Request demonstrations for the routes and storage locations you enable. **Limit:** Initialisation and named history paths do not prove deletion across every storage location or external provider. ### Technical detail: retention and history paths ~~~text Initialisation: src/api/mod.rs History API: src/api/memory.rs ~~~ The initialisation path rejects an invalid saved retention policy. The history API documentation describes rejection when route retention prohibits saved history and restrictions on saved images under a privacy policy. API documentation is evidence of described behaviour; it does not establish every deployed outcome. Product context: [OneVir request paths](https://onevir.onequill.dev/#path). Traceability: [source snapshot and file fingerprints](https://onequill.dev/assets/downloads/onevir-source-snapshot.json). ## Budgets: concurrent spend reservation **Reviewed finding:** The named test presents eight competing attempts to a shared runtime with a two-attempt allowance. It asserts two admissions and the matching reserved amount. **Evidence status:** Test source reviewed. The referenced test was not run for this publication. **Verify in your deployment:** Request concurrent reservation and final settlement evidence using configured provider prices and enabled routes. Include incomplete streams and any counters shared across nodes. **Limit:** This is a specific concurrent reservation scenario. It does not prove every price, stream outcome, settlement path or multi-node counter. ### Technical detail: concurrent reservation test source ~~~text File: src/governance/deployment_runtime_tests.rs Test: deployment_runtime_provider_spend_reservation_is_atomic_under_competing_attempts ~~~ The test launches eight competing attempts, counts admissions and asserts the reserved amount against a two-attempt allowance. The source snapshot records this file as untracked in the reviewed working tree. Ask for its inclusion and executed result in the release evidence you receive. Product context: [OneVir capabilities](https://onevir.onequill.dev/#capabilities). Traceability: [source snapshot and file fingerprints](https://onequill.dev/assets/downloads/onevir-source-snapshot.json). ## Reliability: provider health and fallback **Reviewed finding:** Named source paths describe healthy, degraded, down and refused provider states, cooldown and trial behaviour, and health-aware fallback selection. **Evidence status:** Implementation and source documentation reviewed. Recovery service levels were not established for a deployment. **Verify in your deployment:** Demonstrate provider failure and recovery with your streaming workloads. Record recovery time, partial output handling, fallback decisions and behaviour after a process restart. **Limit:** Provider-health state and selection do not establish complete stream handling, a recovery-time guarantee or restart durability. ### Technical detail: provider health and selection paths ~~~text Provider health: src/proxy/health.rs Fallback selection: src/api/openai.rs ~~~ The health source documents states, cooldown and trial behaviour. The fallback path consults provider health when other endpoints remain to try. Effective provider settings and workload demonstrations are still needed to establish application behaviour. Product context: [OneVir capabilities](https://onevir.onequill.dev/#capabilities). Traceability: [source snapshot and file fingerprints](https://onequill.dev/assets/downloads/onevir-source-snapshot.json). ## Supply chain: a named dependency pin **Reviewed finding:** The reviewed source manifest declares an exact llama-cpp-sys-2 version of =0.1.157 and documents the intent to use one llama.cpp binding version. **Evidence status:** Dependency declaration reviewed. Delivered artifact provenance was not established. **Verify in your deployment:** Obtain the delivered artifact's digest, build provenance, complete dependency inventory and exact model revisions. Assess vulnerabilities for those actual versions and artifacts. **Limit:** One declared dependency pin is not a complete software inventory, proof of the delivered binary's contents or evidence that the dependency has no vulnerabilities. ### Technical detail: dependency declaration ~~~text Manifest: Cargo.toml Dependency: llama-cpp-sys-2 =0.1.157 ~~~ The source package version is 0.2.43 in the captured working tree. This identifies the source package; it does not verify that a particular release artifact was built from these files. The source snapshot supplies the manifest fingerprint and base revision. Product context: [OneVir capabilities](https://onevir.onequill.dev/#capabilities). Traceability: [source snapshot and file fingerprints](https://onequill.dev/assets/downloads/onevir-source-snapshot.json). ## Inference: engine and upstream boundaries **Reviewed finding:** Named sources identify llama.cpp bindings and distinguish GGUF execution from exported accelerator assets. **Evidence status:** Implementation and engine boundary reviewed. Connected inference services were not assessed. **Verify in your deployment:** Inventory every inference engine, model revision and endpoint. Obtain patch, execution-location and isolation evidence for each separately connected service. **Limit:** A finding about a separate engine cannot automatically be applied to this implementation. Local execution also does not establish the behaviour or isolation of an upstream service. ### Technical detail: model format and engine paths ~~~text Bindings: Cargo.toml Accelerator manifest: accelerators/make_manifest.py ~~~ The manifest identifies llama.cpp bindings. The accelerator manifest builder distinguishes GGUF files, which run on llama.cpp, from exported accelerator assets. A separately configured upstream such as vLLM, SGLang, Ollama or LM Studio needs its own evidence for endpoints, patch levels, execution location and memory isolation. Product context: [OneVir request paths](https://onevir.onequill.dev/#path). Traceability: [source snapshot and file fingerprints](https://onequill.dev/assets/downloads/onevir-source-snapshot.json). ## Keeping this record useful The downloadable source snapshot records the base revision, working-tree status and SHA-256 fingerprints of the seven named files. Because some reviewed files contain uncommitted changes, the base revision alone does not reproduce this review. Request the matching source snapshot or release-specific records when evaluating an installation. Recheck the relevant evidence after changes to the release, effective configuration, providers, inference engines or model revisions. Keep article modification dates separate from source-review dates, and record an owner and follow-up date for unresolved questions in the [evaluation checklist](https://onequill.dev/assets/downloads/onevir-evaluation-checklist.md). ## Request release evidence Share your version, deployment mode, enabled providers and controls to evaluate with [OneQuill sales](mailto:sales@onequill.dev?subject=OneVir%20release%20evidence%20request&body=Hello%20OneQuill%20team%2C%0A%0AI%20would%20like%20evidence%20for%20my%20OneVir%20release%20and%20deployment.%0A%0AOneVir%20version%20%2F%20build%3A%0ADeployment%20mode%20(local%2C%20hybrid%20or%20connected%20providers)%3A%0AEnabled%20providers%20and%20inference%20engines%3A%0AControls%20to%20evaluate%3A%0AInstalled%20artifact%20digest%2C%20if%20available%3A%0A%0ARequested%20evidence%3A%20release%20and%20configuration%20scope%2C%20endpoint%20permissions%2C%20retention%20and%20data%20flows%2C%20budget%20accounting%2C%20failure%20recovery%2C%20dependency%20inventory%20and%20inference%20boundaries.%0A%0AReference%3A%20https%3A%2F%2Fonequill.dev%2Fresources%2Fonevir-control-evidence%0ASource%20review%3A%202026-10-07%3B%20source%20package%200.2.43%20(working%20tree%2C%20release%20applicability%20not%20established).%0A%0AThank%20you.). Use the [evaluation checklist](https://onequill.dev/assets/downloads/onevir-evaluation-checklist.md) to record evidence and decisions.