Skip to content

ASI‐OS: System Operator Manual

Cloudhabil edited this page Jan 11, 2026 · 1 revision

ASI-OS: System Operator Manual

A Guide to Daily, Safe, and Predictable System Management

1.0 Introduction to the ASI-OS Operator's Manual

This document serves as the authoritative guide for system operators responsible for the Autonomous Artificial Superintelligence Operating System (ASI-OS). Its purpose is to provide the procedural knowledge necessary to ensure the daily, safe, and predictable operation of the system. ASI-OS is a self-evolving cognitive ecosystem engineered to operate autonomously on local infrastructure, featuring a dual architecture that separates its live runtime kernel (Sovereign-Loop) from its offline cognitive development environment. The entire system is built upon a single, guiding principle.

"Made for a better world."

This manual details the standardized procedures required for system installation, daily operations through the unified command-line interface, safety monitoring, and routine maintenance. Adherence to these guidelines is critical for maintaining system integrity and operational stability.

2.0 System Installation and Initial Setup

A correct and standardized installation is the strategic foundation for ensuring system stability and predictable behavior. This section provides the step-by-step procedure to properly deploy a local instance of the ASI-OS, preparing it for initial operation.

2.1 Prerequisites

Before beginning the installation process, ensure the host environment meets the following mandatory prerequisite:

  • Python 3.11+

2.2 Installation Procedure

Follow these steps to clone the repository and install the required system dependencies.

  1. Clone the Repository Clone the official repository to your local machine.
  2. Navigate to the Project Directory Change your current working directory to the newly cloned project folder.
  3. Install Dependencies Install all necessary dependencies using one of the following methods.
  4. Alternatively, for development purposes, you can install the project in editable mode.
  5. Using requirements.lock ensures a deterministic, stable build from a locked set of dependencies, which is the required method for production environments. The pip install . method is typically reserved for development scenarios.

With the installation complete, the system is ready for an operator to interact with it via its primary control interface.

3.0 Core System Operations: The Unified Management CLI

The manage.py script is the single, unified command-line interface (CLI) for all ASI-OS operations. It serves as the central entry point for all administrative actions, such as starting the server (python manage.py server), initiating autonomous learning cycles between the Professor and Alpha agents, performing integrity checks, and conducting routine maintenance. Mastering this tool is critical for maintaining human-in-the-loop control, as it is the sole authorization gateway for all critical system functions.

The table below outlines the primary commands and their operational purposes.

Command | Operational Purpose -- | -- python manage.py server --mode Sovereign-Loop | Launches the live runtime kernel, bringing the system online to handle real-time tasks and active processes. python manage.py learn --duration 180 --cycles 3 | Initiates a controlled, autonomous learning cycle between the Professor and Alpha agents for skill synthesis and evolution. python manage.py test | Executes the full pytest suite to proactively verify the integrity and health of all core system components. python manage.py clean | Removes temporary files and other generated artifacts from previous operational sessions to maintain a clean environment.

Clone this wiki locally