> ## Documentation Index
> Fetch the complete documentation index at: https://docs.skrmir.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform Overview

> Entry page for AiOS platform capabilities, runtime layering, and environment model.

# Platform Overview

## Audience

This page is for maintainers, implementers, and operators entering the platform docs for the first time.

## Goal and Scope

This page helps you quickly understand:

1. what the formal AiOS runtime model is
2. how platform responsibilities differ from application runtime responsibilities
3. which architecture and environment pages to read next

## Core Concepts

### Runtime layering

AiOS uses:

* a binary install/bootstrap entry
* K3s + image-based services for formal runtime
* stateless control-plane services with externalized state

### Platform responsibilities

The platform is responsible for:

* installation and cluster adoption
* authorization, approval, audit, and task orchestration
* application delivery policies and runtime governance
* data-access gateways and security boundaries
* keeping AI and automation access to database or runtime capabilities under platform policy control

## Standard Workflow

1. the installer detects the environment and initializes K3s
2. platform dependencies and control-plane services are deployed into K3s
3. users access the platform through Web / API, and later CLI / Agent channels, using the same server-side capabilities

## Current Entry Example

Terminal A:

```bash theme={null}
go run ./cmd/aios
```

Terminal B:

```bash theme={null}
curl http://localhost:8080/healthz
```

`aios app up` style subcommands remain future direction, not current behavior of `cmd/aios`.

## Web UI Path

* platform overview
* cluster and environments
* tasks and approvals
* application delivery and deployment history

## Pitfalls / Risk Notes

* the local single-binary skeleton is only for bootstrap/dev validation
* the formal runtime target remains image-based services inside K3s
* the platform governs database, runtime, and cross-boundary capability access; this should not be misread as per-command approval for coding tools inside a DevBox

## Related Pages

* [Architecture](/en/platform/architecture)
* [Light Mode vs Full Mode](/en/platform/cluster/light-vs-full-mode)
* [Environment Model: Dev/Test/Preview/Prod](/en/platform/projects/environments-dev-test-preview-prod)