MLNavigator Research Group project

AdapterOS

Your model. Your machine. Your proof.

Offline-first runtime in development, focused on verifiable execution. The goal is signed runs, versioned adapters, and no outbound telemetry.

In development. Early access is limited and by invitation.

What It Is

Local-First Runtime

AdapterOS is designed to run on your hardware. Models, adapters, and configurations load locally. Inference is intended to run offline.

Adapter Management

Adapter management focuses on loading, switching, and versioning adapters (LoRA, QLoRA) with provenance tracking. Hashing and signing are part of the design.

Proof Generation

Each run is designed to produce a proof pack: hashed inputs, model state, configuration, and outputs. Signed with Ed25519 and chain-linked to previous runs.

Deterministic Execution

Fixed seeds, pinned versions, and declared tolerances aim for repeatable runs within documented numerical bounds.

How It Runs Offline

No Network Calls

The design target is zero outbound connections during inference. No license checks, no telemetry, no updates.

Bundled Dependencies

Dependencies are intended to be vendored. No package manager calls. No CDN fetches.

Air-Gap Compatible

Designed for disconnected networks. Transfer via secure media. Verify on isolated systems.

Offline operation is the primary design target. Network connectivity is treated as a risk in high-assurance environments.

Planned Artifacts

Planned outputs include structured artifacts for audit and verification.

proof.json

Hash chain linking input, model, adapter, config, and output. Ed25519 signature.

manifest.json

Declaration of what was supposed to run. Versions, hashes, configuration.

audit.log

Timestamped event log. Hash-chained entries. Deletion-detectable.

energy.json

Optional Joules/token measurements when energy profiling is enabled.

What It Does Not Do

No Data Exfiltration

AdapterOS is designed without endpoints for outbound data transfer.

No Tracking

No usage analytics or behavioral telemetry in the core runtime.

No Auto-Updates

Updates are intended to be explicit and verified. No background downloads.

No User Accounts

No cloud accounts required. No license servers in the core runtime.

Interested in AdapterOS?

We're exploring pilot deployments with select organizations. Contact us to discuss your requirements.

Request early access Trust Specifications