Skip to content

Architecture and infrastructure

Fleet
Your own machines, pooled for agent work. In the design, a coordinator hands each task to the machine that fits.
Harness
The program that hosts an agent: it gives the agent tools, handles terminal input and output, and keeps a log.
Agent
A software process that pairs a model's reasoning loop with permission to use tools and a workspace, so it can work toward a goal.
Git Worktree
A separate folder linked to one git repository, so several agents can work on different branches at once without colliding. In the design, each agent gets its own.
Digital Sovereignty
The principle that you own your hardware, your data, your code repositories and your choice of models, with no landlord and no lock-in. Vendor terms still apply to vendor tools and cloud models.
On-Device Context
The context for your work (code, files, notes, indexes) kept on the machine that uses it rather than uploaded to a vendor's cloud. A cloud model still receives what an agent sends it.
Private Appliance
Planned: dedicated hardware inside your private network or datacenter, hosting pre-quantized open-weight models. Not live. Talk to us.
Rate Limit Multiplexing
Spreading parallel agent tasks across machines and providers you are entitled to use, so one rate limit does not stall the fleet. It does not remove a provider's limits or terms.

Models and authentication

Local Model
An open-weight model that runs on your own hardware through a local runtime such as Ollama or llama.cpp. In the design, its work stays on the machine.
OAuth 2.1
The authorization standard OmniConflux is designed to use for accounts and connectors, with OpenID Connect for sign-in: Authorization Code flow with PKCE, exact redirect matching and refresh token rotation.
PKCE (Proof Key for Code Exchange)
An OAuth extension that blocks a stolen authorization code from being used on its own. It is a standard way to secure sign-in for native apps and agents.
Bring Your Own Key (BYOK)
You supply your own vendor API key, so billing and the vendor relationship stay yours.
Client ID Metadata Document
A JSON file hosted at a URL that lets an OAuth client declare its identity, logo and scopes without manual registration in a portal. OmniConflux connectors are designed to publish one.

Protocols and sessions

Model Context Protocol (MCP)
An open standard for connecting agents to tools and data sources through structured interfaces.
Agent-to-Agent (A2A)
An open protocol for communication between agents: negotiating sub-tasks, delegating work and exchanging artifacts.
Agent Client Protocol (ACP)
A standard for editors, harnesses and client interfaces to talk to agents, hand work off and negotiate approvals.
Session Forking
In the design, copying an agent session's worktree to a new branch and starting a second agent from the same point, so you can try two approaches side by side.

Verification and security

Verifier
An agent from a different model vendor that checks finished work and returns approve or rework with reasons. In the design, it reads the task, the diff and recorded evidence.
Rework
A verifier's verdict that sends a task back to the builder with the reasons attached, so it can try again.
Cross-Vendor Verification
Checking work from one model vendor with a model from a different vendor, so the check is less likely to share the builder's blind spots. It is a check with recorded evidence, not a guarantee.
Continuous Adversarial Exposure Validation
Scheduled, in-scope checks, re-run as your systems change, on systems you own or are authorized in writing to assess.
Deterministic Vulnerability Verification
Recording a finding only after it is reproduced in a sandbox, so a report carries evidence instead of a guess.
Security Control Efficacy Testing
Agreed checks that confirm whether your existing controls behave as configured.
Continuous Patch and Remediation Testing
Re-testing each fix with the same check that found the issue before it is marked resolved.
Zero Data Retention (ZDR)
A policy under which a provider does not keep customer code, prompts or outputs after processing. OmniConflux will publish a full retention schedule before launch; see the trust page.

Aura and governance

Aura by OmniConflux
An opt-in ad network for OmniConflux's own surfaces, built around on-device topic classification. Runs in closed beta for approved closed beta accounts.
Contextual Ad Broker
The Aura service that matches an advertiser's campaign to a placement using topic tags, and at most one short summary built from those tags, never code or prompts. In closed beta with Aura.

Learn More

Explore the system architecture

Discover how these components are designed to work together in the technical documentation, fleet topology guides, and verification specifications.