-
Notifications
You must be signed in to change notification settings - Fork 0
Project Purpose
This page explains why OSAI exists and what product problem it targets.
Many applications are operationally dumb: they execute business logic but cannot inspect, repair, extend, or redeploy themselves. OSAI targets a future where normal applications embed small CPU-only AI agents that can help maintain and improve the application from inside its own operational boundary.
An app-local agent should be able to:
- understand the application's source code;
- receive a human command;
- inspect relevant files and symbols;
- generate a patch;
- rebuild and test in isolation;
- review the diff;
- sync with Git;
- hot reload, redeploy, or roll back safely.
CPU-only AI is important because it is deployable on ordinary servers, embedded appliances, colocated edge boxes, and developer hardware without depending on CUDA, Metal, GPU scheduling, or a vendor accelerator stack.
CPU-only AI also makes the operating system boundary more useful. If inference, source indexing, networking, build/test work, and Git operations all share CPU and memory resources, then core ownership, memory placement, interrupt routing, and page-fault behavior become first-class performance controls.
The target loop is:
human request
-> app-local CPU-only AI agent
-> source-code index
-> patch generation
-> isolated rebuild and test
-> Git diff review
-> commit or rollback
-> hot reload or redeploy
OSAI exists to make this loop low-latency, observable, and predictable.
This page defines the GitHub Wiki navigation sidebar.
- Architecture
- AI Cells
- CPU AI Runtime
- App Agents
- Memory System
- Networking
- Scheduler and Core Isolation
- Filesystem and Storage
- Driver Model
- Security Model
- Build System
- Build System
- Project Tracker
- Implementation Plan
- QEMU Full OS Core Workdown
- QEMU 100 Completion Plan
- Example Apps
- Codex Work Packages
- Testing and Benchmarking