01
Judgment is typed
Risk, comparison, and clause reading route to reason-1 as Route<Question, Answer>.
Loading
Separator
Put a typed route in front of the models you already call.
Decision
explanation
reason-1
4.2 ms
Loading
Separator
Decision
explanation
reason-1
4.2 ms
Solutions
Clause review is a judgment. It should not share a hop with a summary someone will paste into a letter.
Decision plane
4.2 ms
explanationreason-1
01
Risk, comparison, and clause reading route to reason-1 as Route<Question, Answer>.
02
A summary for counsel is Route<Brief, Document> and goes to write-1.
03
Counsel can see that the answer and the memo were different calls, with different models.
Government requests
Counsel using Separator still get a typed hop for the judgment and a different hop for the memo. Separately, this is when VeloxitySI itself will produce a record to a government. The shape follows the public discipline of a company that refuses informal demands, reviews what is actually binding, produces only what it holds, and tells the customer.
Request on the desk
Outcome
In review
The step in progress has not reached a decision.
VeloxitySI does not give customer records to a government, a police service, or any other authority because the authority asked. An email, a phone call, and a letter that does not bind the company are refused. Asking does not start an export.
A record is prepared only when an order is legally binding on VeloxitySI, the order names data the company actually holds, and counsel has checked both. Until those three are true together, the answer is a refusal or a request that the authority cure the order.
An authority that does not have power over VeloxitySI does not receive data by writing to the company directly. The demand has to arrive through the legal process that actually binds VeloxitySI. Counsel names that process before any record is assembled. This page does not borrow another company's country, and it does not restate a statute.
The order has to name the integration, the period, and the category of record. An order for every customer, or for every document the company has ever seen, is challenged and narrowed. Production does not begin while the scope is still 'everything'.
VeloxitySI does not create a record in order to satisfy an order. If the customer left prompt logging off, prompt text is not in the decision record, and logging is not switched on to fill the gap. A specialist model's generation is not a mailbox VeloxitySI keeps. The consoles on this website run in the browser. They are not sent to VeloxitySI, so there is nothing from them to produce.
Where an order clears the checks, the production is limited to the fields the order requires and the company holds. Those fields are the type, the contract, the model identifier, the latency of the routing decision, and the parts. Prompt text is included only where the customer had already enabled that logging for the named period.
The customer is told. Notice waits only where a court delays it, or where notice would create a risk of injury or death to an identifiable person. A delay is written down. Notice goes out when the delay ends. The customer can object where the law allows.
VeloxitySI can contest an order that is overbroad, that asks for data the service does not hold, or that did not arrive through a process that binds the company. A contest is a legal step. It is not a silent deletion of the request.
If a binding order requires VeloxitySI to keep records that already exist, those records are kept for the period the order states. Preservation does not create logs that were not being kept. It does not open prompt text that was never stored.
A government request is not a reason for the rest of the company to read customer prompts. A decision record is opened by the people the procedure names, for the order in front of them. The same allow-list idea applies inside: a person who is not on the list does not get the record.
An audit is commissioned from a firm that is not VeloxitySI and not Xythera. The scope is written first. The auditor inspects key issuance, the allow-list, the shape of a decision record, whether prompt text is stored, who can read a record, and how an order from an authority is handled. The auditor does not receive customer prompt text in order to do the work. A finding stays open until the fix is checked, or until the remaining risk is accepted in writing. The report is the auditor's document. A customer may request the current report in writing.
This page is the process. It is not a transparency table, because a count of orders has not been published here and a made-up count would be false. It is not a SOC examination, a HIPAA assessment, or a named certification. The security statement remains the control description, and it is still not an audit report.
Held, or not held
The type, the contract, the model identifier, the routing latency, and the parts. Prompt text only where that logging was already on.
Prompt text left off by the customer. A model's generation, unless a written agreement says it is stored. Anything typed into a console on this website.
Independent audit
The audit is independent of the team that ships Separator. It walks the same controls a government request would touch, so the handling of an order is not a story told after the fact.
01
The firm is outside VeloxitySI and outside Xythera. The engagement and the scope are written before anyone looks.
02
The auditor reads key issuance, the allow-list, the decision record, and who inside the company can open a record.
03
Each control is checked against the written procedure. Prompt text is not handed over so the audit can be performed.
04
A gap is a finding. It stays open until a fix is checked again, or until the remaining risk is accepted in writing.
05
The report is the auditor's. A customer requests the current one in writing. This page is not that document.
Now 01 Commission
Only if a binding order covers it and the customer had already enabled prompt logging for that period. If the text was not stored, it is not created later.
No. A direct email is not an order that binds VeloxitySI. The authority has to use the legal process that does.
Yes, unless a court delays notice or notice would risk injury or death. The delay is recorded, and notice follows when it lifts.
It is not this page. Request the current report in writing. The page describes the commission, the inspection, the finding, and the close.
Legal requests and a request for the current audit report go to [email protected]. Mark the subject as a legal request. The security statement and the privacy notice stay the formal documents. Neither one is a certificate.