A record of the handoff
Each decision names the lane. Where a request is divided, the decision names every lane. An application that shows only a final paragraph, and hides the part list, is withholding the record. Separator does not omit it.
Safety
Safety at VeloxitySI.
Separator records which lane received each part of a request. It will not route around an allow-list. This page states those controls.
An allow-list is a refusal
Separator will not select a lane the caller has not permitted. If vision-1 is absent, a request for an image is not sent to vision-1, and it is not redirected to a text model with instructions to describe the image.
A split is not a new permission
Dividing a request does not create permission the original request did not have. Each part remains the caller's request, under the caller's key, on a lane the caller allowed.
1. Scope
This statement describes the safety controls of Separator, the routing product of VeloxitySI, an Xythera company. It applies to the public website at veloxity.si and to the Separator preview. A written production agreement controls where it differs from this statement. This page is not a certification and it is not an audit report.
2. Decision records
Each routing decision identifies the lane that received the request. Where a request is divided, the decision identifies every lane. The application programming interface returns that record. Separator does not drop a part in order to present a single paragraph.
3. Allow-lists
An allow-list is a safety control. Separator will not select a lane that the caller has not permitted. The refusal is the decision. It is not replaced by a call to a different lane.
4. Division of a request
Dividing a request into smaller calls does not create permission that the original request did not have. Each part remains the caller's request, is made under the caller's key, and is sent only to a lane the caller allowed. A refused part stays refused.
5. Models the caller attaches
A caller may place Separator in front of a model it already calls, or in front of an endpoint it hosts. That includes a model published without a refusal layer from a vendor. VeloxitySI does not become the publisher of that model, does not host those weights, and does not rename the output. The allow-list still applies. The decision record still names the lane.
6. Website illustrations
The consoles and diagrams on this website run in the visitor's browser. They illustrate a routing decision. They do not call a model, and they do not transmit the typed text to VeloxitySI. A time shown beside an illustration is a design target, not a measured production benchmark.
7. Limits of this statement
This page does not state that VeloxitySI has completed a SOC examination, a HIPAA assessment, or an independent penetration test. It does not publish a model card for a third-party model. Customers who need those materials from a model publisher should read that publisher's documents.
8. Contact
Questions about this statement, and reports of a decision that looks wrong, may be sent to [email protected]. Name the time and the lane when you have them.
Report a concern
Tell us what the route did.
If a decision, a preview, or this website looks wrong, write to [email protected]. Include the time and the lane when you have them.
Separator
Put a typed route in front of the models you already call.
Decision
explanation
reason-1
4.2 ms