AIKernel.NET is a specification-first repository for Semantic Context OS contracts. The src tree contains the canonical specification projects that define interfaces, DTOs, enums, and external boundary contracts.

As of v0.1.1:

• AIKernel.Abstractions and AIKernel.Contracts export interfaces only.
• DTOs are owned by AIKernel.Dtos.
• Shared enum primitives are owned by AIKernel.Enums.
• AIKernel.Vfs remains a public namespace inside AIKernel.Abstractions; there is no separate AIKernel.Vfs package/project.
• Legacy ambiguous ChatChain names such as IResult and ISemanticHasher are not exported from the ChatChain namespace. Use IChatTurnVerificationResult and IChatTurnSemanticHasher.

Keep all AIKernel.NET packages on the same version line. Do not mix AIKernel.Abstractions v0.1.1 with older AIKernel.Dtos or AIKernel.Enums packages.

For application authors, the safe installation rule is simple: install AIKernel.Abstractions, AIKernel.Contracts, AIKernel.Dtos, and AIKernel.Enums from the same public release family before adding Core, Providers, Tools, Wasm, or Demo packages.

• Purpose: Interface layer (no concrete business logic).
• Main namespaces:
  • AIKernel.Abstractions.Capabilities
  • AIKernel.Abstractions.Context
  • AIKernel.Abstractions.Conversation
  • AIKernel.Abstractions.DynamicSlm
  • AIKernel.Abstractions.Dsl
  • AIKernel.Abstractions.Events
  • AIKernel.Abstractions.Execution
  • AIKernel.Abstractions.Governance
  • AIKernel.Abstractions.History
  • AIKernel.Abstractions.Hosting
  • AIKernel.Abstractions.Kernel
  • AIKernel.Abstractions.Material
  • AIKernel.Abstractions.Models
  • AIKernel.Abstractions.Prompt
  • AIKernel.Abstractions.Providers
  • AIKernel.Abstractions.Rom
  • AIKernel.Abstractions.Routing
  • AIKernel.Abstractions.Scheduling
  • AIKernel.Abstractions.Security
  • AIKernel.Abstractions.Tasks
  • AIKernel.Abstractions.Time
  • AIKernel.Abstractions.Tooling
  • AIKernel.Vfs (Vfs contracts, owned by the Abstractions assembly)
• Project references: AIKernel.Dtos, AIKernel.Enums

• Purpose: Cross-boundary contract interfaces for orchestration/context projections. This package exports interfaces only.
• Main namespace: AIKernel.Contracts
• Project references: AIKernel.Dtos, AIKernel.Enums

• Purpose: POCO/record data carriers and wire metadata key constants only (no business logic).
• Main namespaces:
  • AIKernel.Dtos.Capabilities
  • AIKernel.Dtos.Context
  • AIKernel.Dtos.Core
  • AIKernel.Dtos.DynamicSlm
  • AIKernel.Dtos.Dsl
  • AIKernel.Dtos.Events
  • AIKernel.Dtos.Execution
  • AIKernel.Dtos.Governance
  • AIKernel.Dtos.Kernel
  • AIKernel.Dtos.KernelContext
  • AIKernel.Dtos.History
  • AIKernel.Dtos.Material
  • AIKernel.Dtos.Prompt
  • AIKernel.Dtos.Rom
  • AIKernel.Dtos.Routing
  • AIKernel.Dtos.Rules
  • AIKernel.Dtos.Sandbox
  • AIKernel.Dtos.Security
  • AIKernel.Dtos.SemanticCompilation
  • AIKernel.Dtos.Tokenization
  • AIKernel.Dtos.Time
  • AIKernel.Dtos.Vfs
• Project references: AIKernel.Enums

DTO packages may expose stable metadata key constants for wire formats such as DSL ROM and History ROM. Those constants are part of the serialized contract surface; parsing, validation, and runtime behavior still belong to Core/Common or host implementations. Shared enums such as execution status and prompt option primitives belong to AIKernel.Enums, not AIKernel.Dtos. Capability DTOs describe external module manifests and invocation envelopes for CLI executable, managed assembly, native ABI, DSL ROM, and remote endpoint boundaries. Runtime loading, sandboxing, assembly resolution, and native invocation remain Core/Tools/provider responsibilities. DynamicSLM DTOs describe Model ABI records only. Registry, lineage verification, payload materialization, scheduling, differential distillation planning, SeedSLM discipline enforcement, delegation, thought-artifact dumping, and memory placement belong to Core/Provider implementations behind AIKernel.Abstractions.DynamicSlm. Distillation execution itself is represented as a background offload job so loaders do not block on training work. HATL DTOs describe ledger entries, public anchors, Digital Deeds, verification results, and external cryptographic operator request/result records. Cryptographic runtime belongs to AIKernel.RH-backed operators or other audited Core/HATL modules. Governance DTOs may carry admission replay evidence, critical-operation and computational-complexity gate evidence, and trajectory governance ellipsoid/score/action evaluation records, while AIKernel.Enums owns Semantic IR slot, admission decision/gate, task cost class, and critical-operation requirement vocabulary for Core-side ResultStep/ReplayLog adapters. Semantic Compilation DTOs describe observable semantic state, structural Semantic IR, governed circuit descriptors, finite prototype spaces, semantic distance reports, deterministic synthesis descriptors, and replay-addressable transition descriptors; compiler execution and graph search remain Core/runtime responsibilities.

• Purpose: Shared enum primitives used across the specification layer.
• Main namespace: AIKernel.Enums
• Project references: none

• AIKernel.Abstractions -> AIKernel.Dtos, AIKernel.Enums
• AIKernel.Contracts -> AIKernel.Dtos, AIKernel.Enums
• AIKernel.Dtos -> AIKernel.Enums
• AIKernel.Enums -> (none)

Prohibited examples:

• Abstractions -> Contracts
• Contracts -> Abstractions
• Abstractions -> separate Vfs package/project

AIKernel.Vfs is a public namespace inside AIKernel.Abstractions; the separate AIKernel.Vfs compatibility project was removed in v0.0.4.

• AIKernel.KernelContext project has been decomposed and moved into AIKernel.Dtos.KernelContext (models) and AIKernel.Abstractions (contracts).
• AIKernel.Events project has been decomposed and moved into AIKernel.Dtos.Events (models) and AIKernel.Abstractions.Events (contracts).
• Concrete runtime implementations are out of this repository scope and belong to AIKernel.Core.

• src/tests/AIKernel.Abstractions.Tests: spec-alignment and interface-composition tests.

MIT License Copyright © 2026 Takuya Sogawa