Capability, configuration, and test evidence
Capability
Velociti’s harness controls incoming and outgoing communications through its communication lane. One security plane enforces policies, while monitoring agents watch communications and policy activity 24/7.
Configuration
The specific access rules, destinations, tool permissions, review gates, and retention choices applied to your environment.
Evidence
Observed test results and operating records showing what the configured system actually allowed, blocked, and retained.
Check each part of the deployment
Inference, source storage, backups, logs, and external integrations can run in different locations. The architecture must identify each one and its permitted connections.
- Identity and sources: who can request work and which material they may retrieve.
- Inference and tools: where context is sent, which endpoints are approved, and which actions are allowed.
- Records and retention: what is captured, where it is stored, who can inspect it, and when it is removed.
- Administration and support: how access is granted, reviewed, limited, and revoked.
- Change and recovery: who approves updates, pauses execution, investigates issues, and restores service.
Risks that remain after configuration
No architecture eliminates incorrect model output, prompt injection, compromised sources, or misuse of authorized access. Sandboxes and approval gates help only within their configured scope. Representative tests, denial cases, reviewer training, and an incident response route remain necessary. This website does not assert independent certification or compliance for a customer deployment.
Who is responsible for what
Arriving Together
Design and implement the agreed scope, document configuration and limitations, run the agreed tests, and provide the contracted handover and support.
Your organization
Authorize data use, choose access and retention policies, provide accountable reviewers, approve production actions, and own business and compliance decisions.
Platform and service providers
Provide their contracted technology and services. Licensing, hosting, model terms, and service dependencies need review as part of the selected deployment.
Documents and records to request
Your delivery package should connect the architecture and control map to test cases, sample execution records, unresolved issues, and operating instructions. The scope identifies which artifacts you receive and how each will be accepted.