The requested outcome determines the surface. The user does not need to decompose the problem into tools before EVO can begin.
Genesis Evo / Application Surface
Intent becomes a working surface.
EVO AOS is the private application layer inside Genesis Evo. A user can state the outcome first; EVO can then open the right account app, keep browser evidence visible, or shape a bounded micro app that remains available after the conversation.
Beta operation · launchable shellsWhy this architecture matters
A private tool shaped from natural language can remain in the user's AOS collection instead of disappearing as a one-time chat answer.
EVO and the account owner work against the same bounded app state, files, tasks and visible evidence.
Private micro apps are constrained by ownership, explicit grants, storage and event budgets, version integrity and rollback.
Current operating surface
Swipe the table sideways to compare each layer with its current evidence.
| Layer | Current evidence |
|---|---|
| Account continuity | Owner-scoped state, conflict handling, offline replay and cross-account isolation. |
| Native apps | Private Space, Web Browser, Files, Calendar, Notifications, AOS Store, Evo Synlume, Private Notes, Tasks, Creative Studio, App Builder, Knowledge Organizer, Agent Workspace and Settings. |
| Community | Evo Synlume combines daily sharing, structured discussion, mutual-intent discovery and consented conversation in one governed App. It uses durable cursors and foreground refresh without claiming continuous WebSocket presence or end-to-end encryption. |
| Private apps | Natural-language micro app path on Echo or higher, private runtime surface, lifecycle events, version integrity and rollback. Signal retains reusable Skill creation instead. |
| Agent Workspace | Nexus or higher is required. Signal and Echo show the plan boundary before any job, file mutation or CE use. |
| Browser work | Web Browser retains the bounded view, action status, sources and evidence trail inside AOS. |
| Interaction quality | Keyboard navigation, focus containment, reduced-motion behavior and responsive layouts. |
| Shell inventory | Only launchable shells are published. Draft or unverified apps do not appear in the launcher; shell availability is not operation-release evidence. |
| Operation maturity | AOS is Beta with partial production maturity and is not released inventory. Every app maps its operations to the public capability registry. |
A forward-edge product direction
Most software starts with a catalogue of apps. AOS starts with the user's present intention. It then resolves the bounded capabilities, opens or shapes the smallest useful surface, performs permitted work, verifies the result and preserves the state. The distinction is not a more decorative chat UI; it is a different relationship between intent, software and continuity.
That makes AOS relevant to the emerging class of agent-operated and generative interfaces while retaining something those concepts often omit: account ownership, durable state, inspectable evidence, explicit boundaries and recovery.
AOS means Application Operating Surface. It does not claim to replace a general-purpose phone or desktop operating system, and it does not imply unrestricted control over devices, accounts, networks or external services. The currently launchable shells remain bounded to the capabilities listed above, while those operations retain their own Beta, preview or unavailable status from the public registry.
Shell launchability, operation maturity and account entitlement are separate: opening an App does not mean its mapped operation is released. App Builder can create Skills on Signal, private Apps require Echo or higher, and Agent Workspace requires Nexus or higher. The signed-in membership center shows plan comparison and current purchasing state. New self-service checkout is paused until a same-release production payment receipt is verified.