System Architecture
Summary
EN
System Architecture focuses on package responsibility: contracts define, Core executes, Providers extend, Control governs, Tools inspect, Wasm isolates browser execution, and Doom validates the demo path.
JA
System Architecture は package の責務に焦点を当てます。contracts は定義、Core は実行、Providers は拡張、Control は統治、Tools は検査、Wasm は browser 実行隔離、Doom は demo path 検証を担います。
Why
EN
AdSense review risk increases when pages look like disconnected generated lists. This page gives a real system explanation before linking to generated Reference.
JA
生成一覧だけのページは低品質に見えやすいため、このページでは Reference へ進む前に system としての説明を与えます。
Usage
EN
Trace a feature from contract to runtime package, then to provider/tool integration and finally to the Reference page.
JA
機能を contract から runtime package、provider/tool integration、Reference page へ辿ります。
Examples
flowchart TD\n App["Application"] --> Contracts["AIKernel.NET contracts"]\n Contracts --> Core["AIKernel.Core runtime"]\n Core --> Providers["AIKernel.Providers"]\n Core --> Tools["AIKernel.Tools"]\n Core --> Wasm["AIKernel.Wasm"]\n Core --> Control["AIKernel.Control"]\n Cuda["AIKernel.Cuda13.0"] --> Core\n Doom["AIKernel.Doom demo"] --> Wasm\n Doom --> ProvidersNotes
- Runtime behavior must not be inferred from names alone; check package descriptions and tests.
- Provider and Tool packages are extension surfaces, not contract owners.
- CUDA is optional and external to Core.
See Also
architecture/system-architecture.md