Releases: AIKernel-NET/AIKernel.Core
AIKernel.Core v0.1.1 — Cohering the core runtime
June 10th, 2026 — Cohering the core runtime.
2026年6月10日──コアランタイムを一貫化する。
Cohering the core runtime: execution, context, and semantic state form a governed kernel circuit.
コアランタイムの一貫化──Execution・Context・Semantic State が統治されたカーネル回路を形成する。
Highlights
AIKernel.Core 0.1.1 stabilizes the core runtime layer of the Semantic OS. It brings together the common result semantics, kernel runtime, hosting surface, execution context, VFS, DSL, ROM, time, security, routing, and integration-test boundary into a coherent runtime base for the wider ecosystem.
What's Changed
- Finalized the Core 0.1.1 runtime documentation and release notes.
- Aligned integration test dependencies with official 0.1.1 provider packages.
- Removed stale development-package references from integration test package references.
- Updated documentation to describe AIKernel.Core as the kernel runtime layer of the AIOS SDK.
- Added AIKernel.Monolith context as the official AIOS distribution built on the SDK.
- Improved user-facing documentation for how Core relates to Providers, Control, Wasm, Tools, and Demo.
- Ensured release notes and public documentation consistently use 0.1.1 and the June 10th, 2026 release date.
- Preserved package compatibility while validating the official 0.1.1 dependency surface.
Package Scope
This release covers:
- AIKernel.Common
- AIKernel.Core
- AIKernel.Hosting
- AIKernel.Kernel
- AIKernel.TestKit
Compatibility
- Target version: 0.1.1
- Compatible with AIKernel.NET 0.1.1 packages.
- Intended as the runtime foundation for Providers, Control, Tools, Wasm, CUDA integration, and Demo packages.
Validation
- Release build passed with 0 warnings after dependency alignment.
- Core unit tests passed.
- Integration tests passed.
AIKernel.Core v0.1.0.1
June 9th, 2026 — The Core corrected its own timeline.
2026年6月9日──Core は自らのタイムラインを修正した。
A regression surfaced in 0.1.0: the Core was published from an outdated local package, causing the canonical boundaries to desynchronize from the governed circuit.
0.1.0 では、Core がローカルの旧パッケージを基に公開されてしまい、正準境界が統治回路から 逆行的に逸脱 する事象が発生しました。
0.1.0.1 is the corrective patch in which the Core realigns itself with the intended semantic state and restores the canonical boundary contract.
0.1.0.1 は、Core が本来の意味状態へ 自己再整合 し、正準境界の契約を復旧するための修正パッチです。
[CORE] Canonical Boundary: realigned
[CORE] Execution Circuit: resynchronized
[CORE] VFS Layer: corrected
[CORE] Semantic State: restored
[CORE] Regression Artifact: purged
Today, the Core demonstrates its role as a governed subsystem: it detects its own drift, corrects its boundary, and returns to the semantic circuit.
今日、Core は統治サブシステムとしての本質を示しました── 自らの逸脱を検知し、境界を修正し、意味回路へ復帰したのです。
AIKernel.Core v0.1.0.1
This is a patch release for the AIKernel.Core package family.
v0.1.0.1 corrects the package state after the initial v0.1.0 publication while preserving compatibility with the official AIKernel.NET contract packages v0.1.0.
Packages
- AIKernel.Common
0.1.0.1 - AIKernel.Core
0.1.0.1 - AIKernel.Kernel
0.1.0.1 - AIKernel.Hosting
0.1.0.1 - AIKernel.Providers.MicrosoftAI
0.1.0.1 - AIKernel.TestKit
0.1.0.1 - aikernel-net
0.1.0.1
Changes
- Updated NuGet package metadata to
0.1.0.1 - Updated Python package metadata to
0.1.0.1 - Updated Python managed assembly discovery to target the patch package version
- Fixed test ambiguity around
KernelProviderRoutingDecision
Compatibility
This release continues to depend on the official AIKernel.NET contract packages:
- AIKernel.Abstractions
0.1.0 - AIKernel.Dtos
0.1.0 - AIKernel.Enums
0.1.0
Verification
- .NET Release tests passed
- Python tests passed
- PyPI wheel metadata check passed
Release AIKernel.Core v0.1.0
June 9th, 2026 — The canonical boundaries close into a circuit.
2026年6月9日──正準境界は回路として閉じた。
Core 0.1.0 stabilizes the canonical boundaries: Context, Execution, VFS, and Semantic State now form a governed circuit.
Core 0.1.0 は正準境界を確立──Context・Execution・VFS・Semantic State が統治回路として結線される。
[CORE] Context Boundary: stabilized
[CORE] Execution Circuit: closed
[CORE] VFS: mounted
[CORE] Semantic State: governed
Today, the Core becomes a fully governed structural backbone.
今日、Core は完全に統治された構造的背骨となりました。
AIKernel.Core v0.1.0
AIKernel.Core v0.1.0 is the first executable runtime baseline of the AIKernel ecosystem.
This release aligns the Core runtime package family with the official AIKernel.NET contract packages v0.1.0 and establishes the executable foundation for Result-based composition, replayable semantic steps, Kernel orchestration, provider integration, hosting, and Python package discovery.
Highlights
- Aligns with official AIKernel.NET contract packages v0.1.0:
AIKernel.AbstractionsAIKernel.DtosAIKernel.Enums
- Provides executable runtime primitives:
ResultOptionEitherResultStep- ReplayLog / SemanticDelta semantics
- Provides DSL and ROM runtime adapters.
- Provides Kernel orchestration and provider routing helpers.
- Provides hosting integration for dependency injection.
- Provides Microsoft.Extensions.AI provider integration.
- Keeps GPU and Native ABI implementations outside Core as external Capability packages.
- Keeps MemoryRegion / MemoryMapper as Core-owned runtime adapter surface for the v0.1.0 baseline.
- Provides the official
aikernel-netPython wheel for managed assembly discovery and functional primitives.
NuGet Packages
AIKernel.Common0.1.0AIKernel.Core0.1.0AIKernel.Kernel0.1.0AIKernel.Hosting0.1.0AIKernel.Providers.MicrosoftAI0.1.0AIKernel.TestKit0.1.0
PyPI Package
aikernel-net0.1.0
Install:
pip install aikernel-net==0.1.0Verification
- .NET restore succeeded.
- .NET Release build succeeded.
- .NET tests passed:
- 400 passed / 0 failed
- Python tests passed:
- 59 passed / 1 skipped
- Python wheel build succeeded.
- twine check passed.
Package Boundary
AIKernel.Core is the executable runtime layer.
AIKernel.NET remains the contract/specification layer. AIKernel.Core consumes the official AIKernel.NET v0.1.0 packages and provides runtime behavior, adapters, orchestration, and provider integration on top of that contract surface.
GPU, CUDA, Native ABI, tools, control-plane, and demo implementations remain in their dedicated repositories/packages.
AIKernel Python 0.0.5.1 — aikernel-net PyPI registration
June 6th — The Kernel detected a namespace collision.
2026年6月6日──カーネルは名前空間の衝突を検知した。[KERNEL] Python namespace: contaminated [KERNEL] Collision source: external package "aikernel" [KERNEL] Mitigation: rename to "aikernel-net" [KERNEL] Status: identity restoredv0.0.5.1 is the first corrective patch I applied to protect AIKernel’s own namespace — its boundary of identity.
v0.0.5.1 は、AIKernel が自分の名前空間(境界)を守るために、私が適用した最初の修復パッチである。Today, I learned a simple truth: “A name is structure, and structure is power.”
私は今日、ひとつの教訓を得た。「名前は構造であり、構造は力である」。
AIKernel Python 0.0.5.1 — aikernel-net PyPI registration
This release prepares the AIKernel.NET Python binding for publication on PyPI as aikernel-net.
Highlights
- Renamed the Python distribution package to
aikernel-net - Standardized the Python import name as
aikernel_net - Avoided collision with the existing unrelated PyPI package named
aikernel - Added package version
0.0.5.1 - Updated documentation for PyPI-based installation and usage
Install
pip install aikernel-netAIKernel.Core v0.0.5 - First Core Runtime Package Family
June 6th, 2026 — The Kernel achieved symmetry. 2026年6月6日 — カーネルは初めて対称性を獲得した。
On this day where 6 and 6 face each other, AIKernel.Core recorded its first symmetric boot.
6 と 6 が向かい合うこの日に、 AIKernel.Core は初めて 左右対称のブートログ を刻んだ。
The system moved from “contracts without implementation” into a deterministic semantic OS.
これまでの「実装を持たない契約」から一歩進み、 Core は 決定論的セマンティックOS として形を得た。
DSL flows, monads compose, ReplayLog preserves causality, and the CapabilityGraph awaits the outside world.
DSL は流れ、モナドは結合し、 ReplayLog は因果を保存し、 CapabilityGraph は外部世界を待ち受ける。
コード
[CORE] v0.0.5 initialized on 2026-06-06 [CORE] Determinism: ON [CORE] Symmetry: VERIFIED [CORE] Awaiting external capabilities...Today marks the moment the Kernel began its real execution.
今日、カーネルは本当の “実行” を開始した。
AIKernel.Core v0.0.5
This release publishes the first AIKernel.Core package family aligned with AIKernel.NET contracts v0.0.5.
Packages
Publish in this order:
- AIKernel.Common
- AIKernel.Core
- AIKernel.Kernel
- AIKernel.Hosting
- AIKernel.Providers.MicrosoftAI
- AIKernel.TestKit
Highlights
- Core runtime packages aligned with AIKernel.NET
Abstractions,Dtos, andEnumsv0.0.5 - Result / Option / Either / Try primitives and LINQ-style monad composition
- Deterministic
ResultStepreplay metadata and semantic pipeline support - Kernel execution, governance, provider routing, VFS/ROM, DSL ROM, and History ROM foundations
- CPU-only Python binding as universal
py3-none-anywheel - CUDA and Native ABI kept outside Core as external Capability packages
- Documentation updated for Core release checks and CUDA split distribution
Python
The aikernel Python package is CPU-only by default and does not include CUDA, LibTorch, or native ABI payloads.
CUDA
CUDA support is opt-in. External CUDA Capability packages may use split distribution:
- NuGet.org metadata package
- GitHub Release full runtime package
Validation
- .NET tests: 371 Core tests + 21 integration tests passed
- Python tests: 60 passed
- NuGet pack completed
- Python wheel built as
aikernel-0.0.5-py3-none-any.whl
License
Apache License 2.0
AIKernel.NET Core v0.0.0 — Initial Repository Setup: First Blink
AIKernel.NET Core v0.0.0 — Initial Repository Setup
May 9th — The Kernel blinked for the first time.
5月9日 — Kernel が初めて目を開けた日。
AIKernel.NET Core v0.0.0 is the first public release of the Core implementation repository.
This release does not execute inference yet.
It does not generate text.
It does not mount ROM.
It does not route providers.
It does not enforce governance.
But today, the structure became observable.
AIKernel.NET Core v0.0.0 は、Core 実装リポジトリの最初の公開リリースです。
このリリースでは、まだ推論は実行されません。
テキスト生成も行いません。
ROM のマウントも行いません。
Provider ルーティングもまだありません。
Governance の強制もまだ行いません。
しかし今日、構造は観測可能になりました。
What This Release Contains / このリリースに含まれるもの
- Initial repository structure
src/andtests/layout- Project skeletons for Core / Kernel / Hosting / Providers
- Initial test project layout
- README / README-jp documentation
- Repository-level roadmap toward v0.1.0
- Initial alignment with AIKernel.NET Canonical Contracts
- 初期リポジトリ構造
src/とtests/の配置- Core / Kernel / Hosting / Providers のプロジェクト骨格
- 初期テストプロジェクト構成
- README / README-jp ドキュメント
- v0.1.0 に向けたリポジトリ単位のロードマップ
- AIKernel.NET Canonical Contracts との初期整合
What This Release Does Not Contain Yet / まだ含まれないもの
- Runtime execution
- VFS implementation
- ROM loading
- ContextSnapshot generation
- Prompt composition
- Provider execution
- Governance enforcement
- Deterministic Replay
- ランタイム実行
- VFS 実装
- ROM 読み込み
- ContextSnapshot 生成
- Prompt Composition
- Provider 実行
- Governance 強制
- Deterministic Replay
Why This Matters / このリリースの意味
This is not yet the Kernel running.
It is the bootloader becoming visible.
AIKernel.NET v0.0.1 established the Canonical Contracts.
AIKernel.NET Core v0.0.0 creates the place where those contracts will become executable.
This release marks the transition from contract definition to runtime construction.
これは、まだ Kernel が動き始めたリリースではありません。
これは、ブートローダーが観測可能になった段階です。
AIKernel.NET v0.0.1 は Canonical Contracts を確立しました。
AIKernel.NET Core v0.0.0 は、その Contract が実行可能になるための場所を作ります。
このリリースは、契約の定義 から ランタイムの構築 へ移行するための最初の一歩です。
Repository Role / リポジトリの役割
AIKernel.NET defines the contracts.
AIKernel.NET Core proves them through implementation.
AIKernel.NET は契約を定義する。
AIKernel.NET Core はそれを実装によって証明する。
This repository is where the Knowledge OS begins to take runtime form.
このリポジトリは、Knowledge OS がランタイムとして形を取り始める場所です。
Next / 次へ
v0.0.0 defines the place.
v0.0.1 will begin filling it with motion.
v0.0.0 は場所を定義する。
v0.0.1 はそこに動きを与え始める。
Closing / 結び
The Kernel does not speak yet.
It does not act yet.
But today, the bootloader of the Knowledge OS opened its eyes —
without even printing “Hello, World.”
まだ Kernel は語らない。
まだ Kernel は実行しない。
しかし今日、知能 OS のブートローダーは
“Hello, World” すら出さずに目だけ開けました。
Tomorrow, it begins to move.
明日、Kernel は動き始める。