AIKernel.Control is the physical execution layer for AIKernel semantic graphs. Use this documentation when you need to run, inspect, or package Control engines for .NET and Python hosts.

These docs describe Control as the AIOS SDK governance, security, and physical execution layer. Control maps semantic graphs from Core onto explicit policies, deterministic schedulers, diagnostics, and execution engines.

AIKernel.Monolith is the official AIOS distribution now in development. It is planned as the standard reference distribution that integrates the control plane with the Semantic OS layers after the 0.1.x line stabilizes.

• User Guide
• Architecture
• Bonsai mapping
• Bonsai-1.7B built-in provider
• Execution engine
• Q1_0 CPU execution kernel
• Control pipelines
• Python governance wrapper
• Licensing

• Read the User Guide when you want the install commands and the smallest deterministic emulator/CPU validation path.
• Read Architecture when you need to understand why semantic graphs are owned by Core while physical execution engines are owned here.
• Read Bonsai mapping before wiring Bonsai-style graphs to emulator, CPU, or GPU execution.
• Read Python governance wrapper when you are consuming Control from Python and need to confirm that Python is only a managed assembly bridge.

Start with CPU and Emulator validation before binding GPU execution:

dotnet build AIKernel.Control.slnx -c Release
dotnet test AIKernel.Control.slnx -c Release --no-build

• Install the matching AIKernel.Control.* packages.
• Mount model assets through VFS/ROM instead of local ad hoc paths.
• Use CPU/Emulator packages for deterministic validation before binding GPU execution.
• Use the Python wrapper only as a thin managed assembly bridge.