Security
Keep confidential source data in an environment you control.
adapterOS is designed so protected work can remain in a customer-controlled environment instead of requiring a copy in an unfamiliar vendor-managed knowledge base. The exact boundary depends on the selected build, deployment, and approved destinations.
The selected boundary
Sources, intermediate work, policy decisions, and records stay where the configuration says they belong.
At the boundary, the configured action may allow an approved route, transform the output, refuse the transfer, or continue the work inside the approved environment.
- In scope
- Approved sources, requested work, policy decision, intermediate work, and retained records according to the selected configuration.
- At the boundary
- Allow · Transform · Refuse · Continue inside
- Still a human decision
- The record supports review; it does not certify the source or decide acceptance by itself.
- 01Approved sources
Only the selected source set enters the work.
- 02Protected work
Intermediate work stays in the controlled environment.
- 03Boundary decision
Allow · Transform · Refuse · Continue inside
- 04Eligible outcome
Approved route proceedsWrong route stops; work continues inside
Records and reviewability
Reconstruct the request, the route, and the human decision.
The configured record can preserve what was requested, which approved sources were in scope, the policy version, the selected route, execution state, output and limits, and the reviewer’s disposition.
- Request
- Question, requested action, and destination.
- Authority
- Approved source set and applicable policy version.
- Execution
- Selected route, run state, answer, support, and limits.
- Disposition
- The authorized person's acceptance, revision, rejection, or escalation.
Regulated environments
Apply the same boundary discipline where handling rules are consequential.
Customer-controlled deployment, explicit source scope, destination rules, and human review can support a regulated workflow design. Applicable requirements remain customer- and counsel-determined.
- Protected materialControlled revision packet
- Requested destinationUnapproved external AI
- Policy appliedThis document class is not approved for that destination
- Protected continuationWrong route stopped
The packet remains inside the configured boundary. The person continues with the approved source set inside adapterOS.
Illustrative review state · not a certification or compliance determination
Controlled-document teams
Operations where document handling rules determine which destinations and workflows are allowed.
Compliance-owned AI programs
Teams that need reviewable evidence that configured policy was applied to real work.
Security and data owners
People responsible for the source boundary, eligible execution routes, records, and escalation.
Architectural alignment is not certification, attestation, a legal guarantee, or a promise that every selected build supports offline or air-gapped operation. Exact deployment capabilities belong in the evaluation discussion.
Security contact
Report security issues to security@adapteros.com. We acknowledge reports within 2 business days and provide an initial assessment within 5 business days.
Review the boundary on work that matters
A Controlled evaluation names the approved corpus, requested destination, policy action, selected environment, reviewer duties, and success criteria before confidential work begins.