Keep confidential information out of the wrong AI—and keep the work moving

adapterOS checks each request against policy before it runs, then runs it on a local runtime inside the customer environment, with no outbound route. The answer comes back with its sources, its limits, and a record a reviewer can act on.

Start an evaluationWatch one request take two routes

Two conversations. Same prompt. Different route.

01 · Ordinary AI chat

The conversation looks normal

An analyst attaches a supplier agreement and asks what it obliges the company to do. The answer is useful. Nothing on screen says where the file went.

AssistantNew conversation

You09:42

supplier-agreement.pdfPDF · 14 pages

Can you review this supplier agreement and tell me what our obligations are?

Assistant

The agreement contains several obligations worth reviewing before signing. I’ll break down the payment terms, termination provisions, and confidentiality requirements.

You pay each undisputed invoice within 45 days of receipt. Either side can end the agreement for convenience with 90 days’ written notice. Both sides must protect each other’s confidential information, and that duty continues for five years after the agreement ends.

Example conversation. Nothing you type is sent.

01 · The route it took

The document left the boundary

To answer, the assistant sent the whole file to an external model endpoint. No rule was checked first, and a copy now sits outside the organization’s control.

This is an illustrative failure, not a claim about any particular AI service.

Request routeNo policy evaluated
  1. supplier-agreement.pdfConfidential · Contracts
  2. Assistant appUploads the prompt and the attachment
  3. Organization boundary
  4. External model endpointOutside the boundary · holds a copy of the fileNot an approved destination

02 · The same request through adapterOS

The route is decided before anything moves

Same prompt, same file. This time the request runs inside adapterOS. Policy is evaluated first: an external destination is not approved for this document, so the work continues on the local runtime.

Request routecontracts-confidential v3
  1. supplier-agreement.pdfConfidential · Contracts
  2. Policy checkDocument, destination, requested actionExternal destination: stopped
  3. Local runtimeInside the customer environmentApproved route
  4. Organization boundary
  5. External model endpointNothing sent

Running on a local runtime with no outbound route is how the current build works. Classifying a document and stopping a requested external destination is planned; it is shown here as intended behavior.

02 · What comes back

The answer arrives with its sources

The reply reads almost the same. The difference is where the file went, and what is kept: the route taken, the policy version, the sources used, and what the answer could not cover.

AssistantNew conversation

You09:42

supplier-agreement.pdfPDF · 14 pages

Can you review this supplier agreement and tell me what our obligations are?

adapterOS · Protected route

An external destination is not approved for this document. Continuing on the local runtime inside your environment.

AssistantRun R-2041 · local runtime

The agreement contains several obligations worth reviewing before signing. I’ll break down the payment terms, termination provisions, and confidentiality requirements.

You pay each undisputed invoice within 45 days of receipt.§4.1 Either side can end the agreement for convenience with 90 days’ written notice.§9.2 Both sides must protect each other’s confidential information, and that duty continues for five years after the agreement ends.§11.1§12.4

Based on supplier-agreement.pdf v3 only. §7.3 refers to Exhibit C, which is not in the source set, so service-level obligations are not covered here.

Example conversation. Nothing you type is sent.

Illustrative example using fabricated records. It is not a customer result, legal advice, performance claim, availability claim, or product-market decision.

One answer is a demonstration. A session is the work.

The analyst asks a follow-up. An exhibit turns out to be missing. Counsel sends the result back. A revised draft arrives and the question is run again. The workspace page shows that whole session inside the application.

Explore the adapterOS workspace

After the answer

What you can check afterwards, and where

  • Where the documents went

    The destination that was asked for, the policy that applied, and the route that ran instead.

  • What the answer rests on

    The exact sentence behind each citation, the two clauses that disagree, and the exhibit that was never provided.

  • What changed on the rerun

    Which source was revised, which finding it settled, and which two are still open.

  • Who decided

    What the system recorded about the run, kept apart from the disposition a named reviewer entered.

  • What exists today

    Each setting marked as in the current build, set per deployment, planned, or not available.

Evaluate it on one workflow of your own

Start an evaluationHow an evaluation works