TheOneAI OS
App Directory

Apps TheOne can run.

Apps are focused work surfaces on top of the same OS: TheOne governs intent and policy, OneAI reasons, and OneClaw executes through workers and connectors.

Phases3
Apps28
Connected16
TheOneIntent, policy, workflow, proof, memory
OneAIPlanning, reasoning, writing, judgment
OneClawWorkers, connectors, browser, desktop, APIs
L19Multi-App Automation OS

Run and Apps route proven OneClaw workers into real user-facing workspaces.

L20Parallel Agent Runtime

Planner, Executor, Reviewer, Policy, and Memory roles coordinate before execution.

L21Installable OS

Apps, workers, connectors, and policy packs become versioned installable packages.

L22Self-Evolving OS

TheOne learns from failures and proposes safe upgrades with simulation and rollback.

L24App Memory OS

Focused Apps generate reusable memory packs, not just one-time outputs.

L25Autonomous Workspace OS

Apps can become ongoing workspaces with cadence, limits, proof, and circuit breakers.

L26Mission Control Runtime

Each workspace has its own timeline, policy, memory, proof, packages, and diagnosis.

L27Durable Recovery OS

Queues, replay, resume, circuit breakers, and recovery paths become first-class.

L28Tenant Identity OS

Users, roles, consent, credentials, and workspaces become scoped boundaries.

L29Package Marketplace

Apps, workers, connectors, and policy packs can be signed, installed, upgraded, and rolled back.

L30Simulation OS

Plans are scored, simulated, and blocked before risky autonomous execution.

L31Bridge Mesh

Cloud workers, local computers, browsers, and devices become a secure execution mesh.

L32Memory Graph OS

People, projects, proof, files, tasks, and decisions become connected knowledge.

L33Self-Evolving OS+

TheOne proposes, simulates, applies, monitors, and rolls back its own upgrades.

L34Universal AI OS

The user states an outcome once; TheOne composes Apps, agents, workers, policy, memory, and proof.

Final OS Ladder

The L27-L34 layers TheOne needs to become a universal AI operating system, now represented as system-readable blueprint data.

L34 target

L27 · Durable Runtime / Recovery OS

partial

TheOne can recover work instead of losing it when a worker, approval, or provider fails.

queue leaseretry scheduledead-letter routereplay/resumecross-App handoff

L28 · Tenant / Identity / Role OS

planned

Teams can safely share TheOne without sharing every secret, worker, approval, or memory.

tenant scoperole scopeconsent recordcredential bindingidentity connector

L29 · Signed Package Marketplace

partial

TheOne can grow through packages without hardcoding every future capability.

signed manifestversion lockcompatibility solverinstall contractrollback plan

L30 · Agent Evaluation / Simulation OS

partial

Automation becomes safer because TheOne can rehearse work before it acts.

quality gatecritic verdictgolden task evalsimulation receiptrisk block

L31 · Cross-Device / Local Bridge Mesh

partial

TheOne can choose the right execution surface: cloud, browser, local Mac, or future device.

device registrybridge heartbeatworker capability mapdevice policylocal proof

L32 · Memory Graph / Knowledge OS

partial

TheOne remembers useful context as relationships, not just logs.

entity graphproof linkproject memorypreference memorysemantic recall

L33 · Self-Evolving OS

partial

TheOne improves its own Apps, policies, workers, prompts, and workflows under governance.

upgrade proposalsimulation gateapproval gatepatch bundlerollback bundle

L34 · Universal AI Operating System

partial

The user states the goal once; TheOne keeps coordinating until the outcome is done.

outcome commandApp compositionagent quorumworker executionproof/memory closure
Phase 1

Core Apps

The first product surfaces people can use directly.

Phase 2

Work OS Expansion

Everyday business systems TheOne can coordinate.

Phase 3

Industry OS & Guarded Actions

Vertical workflows and high-impact operations that require stronger policy.