​

Operations Overview

​

Audience

​

Goal and Scope

1. the difference between bootstrap/install and formal runtime
2. how authentication, authorization, and approval form one guardrail chain
3. how logging, audit, and observability are separated

​

Core Concepts

• the binary entry handles bootstrap
• formal runtime depends on K3s + image-based services
• the control plane is stateless-first, with externalized state
• the security chain is AuthN -> AuthZ -> Approval -> Execute -> Audit

​

Standard Workflow

1. complete install/bootstrap
2. transition into K3s formal runtime
3. govern runtime risk through logs, audit, tasks, and approvals

​

CLI Examples

make check-p0-contracts
aios approval request --action deploy.app.update --resource app:project/prod/my-api

​

Web UI Path

• approval center
• task center
• platform health and logging views

​

Pitfalls / Risk Notes

• audit is not just another application log stream
• if critical state still depends on one process memory space, the formal runtime goal has not been achieved

​

Related Pages

• Authentication and Authorization Model
• Logging Architecture