Ways to obtain and run an AO
Compare authorized sessions, background delivery, containers and planned managed hosting.
Choose a continuation mechanism
Start with a complete separate blank and an authorized client. Source acquisition, state initialization, opening a client and starting a service are different actions. None follows automatically from the previous one.
| Option | Communication and continuation | Prerequisites | Status |
|---|---|---|---|
| Authorized session | Client conversation; resume from saved state in another session | Complete blank, Python 3.11+, Git, authorized client and real delegation | Documented local prototype |
| Background launcher | Durable messages/events/deadlines trigger native turns | Initialized instance, service process, client authorization and OS configuration | Implemented locally; historical tests are version-specific |
| Container | Planned isolated environment; communication/continuation must be designed | Image, persistent storage, client access and verification | Images and automatic deployment not supplied |
| Managed hosting | Planned managed communication and continuation | Hosting, maintenance, backup and billing implementation | Product direction; no purchase or launch offered |
Obtain the blank before following local commands
The inspected source has no origin remote and its documentation does not supply a verified public acquisition URL. Obtain a complete uninitialized repository or archive from the owner. The first-prototype guide explicitly starts from an already available local source; it is not a public download instruction.
What the current evidence supports
The inspected blank identifies itself as v0.3.0-dev. Local mechanisms and historical native-client tests are documented separately. Fifteen-minute service observations do not prove round-the-clock operation of every client or host-reboot recovery. No runtime trials were repeated for this website update.
Sources & context
Reference edition 0.1 · 2026-10-15. Read the editorial method.