Architecture
What runs where, and what it depends on
adapterOS runs on hardware the customer controls. This page lists what an administrator sets, and marks every item as in the current build, set per deployment, planned, or not available.
Settings
Six things an administrator decides
Choose a section. The rows follow the product’s configuration categories; the status column is the point.
- In the current buildexists and is exercised in the product today
- Set per deploymentdone with MLNavigator for a specific deployment
- Planneddesigned, not yet built or not yet qualified
- Not availabledoes not exist and is not scheduled
Where documents come from
- File uploadPDF, Word, Excel, PowerPoint, Markdown, and plain textIn the current build
- Connected foldersA registered directory, rescanned on requestIn the current build
- Git repositoriesA registered repository as a sourceIn the current build
- Exclusion rulesAn ignore file keeps named paths out of the source setIn the current build
- Other document systemsConnected case by case during an evaluation; no packaged connectorSet per deployment
Where information may go
- Local runtimeThe only execution destination; inside the customer environmentIn the current build
- External model endpointsNone. The serving runtime has no outbound routeIn the current build
- Document exportA reviewed result can be exported as a Word documentIn the current build
- Per-destination rulesNaming approved and refused destinations by document classPlanned
- Handoff from another AI toolContinuing a stopped request from an external assistantPlanned
Where the model runs
- Apple silicon MacModels run in-process on the host that holds the documentsIn the current build
- Other hostsA second local backend exists; it has not been qualifiedPlanned
- More than one nodeConfiguration exists; it has not been verifiedPlanned
What is checked before a run
- Policy evaluationEach run is evaluated before execution; allow, warn, or deny is recorded with itIn the current build
- Policy historyChanges to a workspace’s execution policy are kept as versionsIn the current build
- Source admissionRules decide which files may enter the source setIn the current build
- Document classificationLabels such as Confidential · Contracts that policy can act onPlanned
Who can do what
- Sign-inIndividual accounts with passwords; API keys for integrationsIn the current build
- RolesAdmin, Operator, and ViewerIn the current build
- WorkspacesSources, sessions, and policy are separated per workspaceIn the current build
- Reviewer sign-offA disposition is entered under the reviewer’s own accountIn the current build
- Single sign-onNo SAML or OIDC integrationNot available
What a deployment depends on
- HardwareAn Apple silicon Mac with enough memory for the chosen modelIn the current build
- NetworkNo internet access is needed to answer; the runtime is built to work without itIn the current build
- InstallationSet up with MLNavigator for each evaluation; no self-serve installerSet per deployment
- CertificationsNone held or claimedNot available
Illustrative example using fabricated records. It is not a customer result, legal advice, performance claim, availability claim, or product-market decision.
Interfaces
Three ways in, one set of rules
Workspace
The web application shown on the Workspace page: conversation, documents, runs, and review.
In the current buildCommand line
The same questions, ingestion, and record checks from a terminal, for automation.
In the current buildAPI
A local HTTP interface for integration with an existing review process.
In the current build
Which interface a request arrives through does not change the policy applied to it, the record kept about it, or who may review it.
Direction
The control plane for private AI
The contract review on this site is one workflow. The same pieces govern any other: which sources are in scope, which routes are eligible, and what a route may receive.
That is the direction, not a description of today. Today the product handles documents, one local route, and review. Recurring workflows and additional approved routes are planned and are not offered as current capability.