> ## 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.

# Bootstrap: Full Mode

> Production-oriented bootstrap path with a fuller dependency footprint, governance baseline, and closer alignment to the formal runtime model.

# Bootstrap: Full Mode

## Audience

This page is for operators and maintainers who need a production-oriented bootstrap flow closer to the formal runtime shape.

## Goal and Scope

This page explains the full-mode bootstrap flow and why it is closer to the final runtime baseline.

## Core Concepts

* full mode still begins with the binary bootstrap entry
* the goal is to move the control plane and dependencies into K3s image-based runtime as early as possible
* environment, approval, audit, and persistence expectations are closer to formal production

## Standard Workflow

1. complete preflight and source selection
2. install or adopt K3s
3. deploy PostgreSQL, object storage, pooler, and other core dependencies
4. deploy the control-plane services
5. initialize environments, quotas, policies, and default security baselines

## CLI Examples

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

## Web UI Path

Choose full mode in the install wizard and continue through the more complete bootstrap flow.

## Pitfalls / Risk Notes

* full mode is closer to the formal runtime, but it is not a different runtime model
* if key state is still backed by in-memory stubs, full mode still does not meet the final runtime goal

## Related Pages

* [Start Here](/en/getting-started/index)
* [Light Mode vs Full Mode](/en/platform/cluster/light-vs-full-mode)