Protection
What happens before a document reaches a model
A request names its sources, a destination, and an action. Policy is evaluated on those before anything runs. A refused destination does not end the work; the request continues where it is allowed to run.
One request, two routes
The route that was asked for, and the route that ran
Switch between them. The request, the classification, and the policy are the same in both; only the destination and its outcome differ.
1 · Request
M. Okafor asks: “Can you review this supplier agreement and tell me what our obligations are?”
supplier-agreement.pdfv3
2 · Source classification
- supplier-agreement.pdf
- Confidential · Contracts
3 · Policy decision
- External model endpointDeny
- Local runtimeAllow
4 · Destination
External model endpoint
Outside the organization boundary.
Stopped before dispatch
No part of the document was sent. The request was not dropped: it continues on the approved route.
Local runtime
Inside the customer environment, with no outbound route.
Executed here
The same question ran against the same document and produced run R-2041.
Illustrative example using fabricated records. It is not a customer result, legal advice, performance claim, availability claim, or product-market decision. The diagram shows intended configured behavior; the list below says which parts exist today.
Status
Which parts of this exist today
Local execution
The model runs on the host that holds the documents. The serving runtime has no outbound route, so there is no external destination to reach.
In the current buildPolicy evaluation
Each run is evaluated before execution, and the decision is kept with the run.
In the current buildSource admission
Rules decide which files may enter a session’s source set at all.
In the current buildDocument classes and destination rules
Labelling a document and refusing a named destination for that label, as the diagram shows.
PlannedHolding an unclassified source
When a source cannot be classified, the request waits or the person is asked.
PlannedHandoff from another AI tool
Continuing a request that began in an external assistant. adapterOS does not observe or intercept other applications.
Planned
Scope
What a stopped route does not mean
General AI tools remain useful for work a company permits them to receive. adapterOS is where the work continues when the documents cannot go there.
A stopped route is a decision about one request. It is not a scan of the organization, a monitoring product, or evidence that nothing has ever left by another path.
A return to the person who asked is not an export. Sending a result to another system is a separate, named action.