Japanese version: Semantic Context OS ビジョン

Semantic Context OS Vision

1. Summary

AIKernel.NET's final architecture target is the Semantic Context OS. This OS governs AI reasoning, material evidence, and generated expression as independent system objects, and structurally enables branching, reuse, auditing, and committee reasoning.

2. Principles and Specification

(See existing specs for full details.)

• 01 Category Separation Principles
• 02 Signed Prompt Governance Spec
• 03 ROM Core Spec
• 04 Model Routing Spec
• 06 Replay Dump Spec
• 08 Execution Contract Architecture
• 09 PDP Guard Decision Plane
• 14 Signed Prompt Governance Workflow

3. System Integrity Requirements

To guarantee OS-level reliability and determinism, the following physical and logical constraints are mandatory.

3.1 Required Interfaces

• SIR-001: ISemanticHasher and IRomCanonicalizer MUST be adopted as required interfaces in ROM Core.
• SIR-002 Immutable Execution Constraints: IExecutionConstraints MUST be specified as an immutable record to prevent runtime tampering.

public sealed record ExecutionConstraints(\n    IReadOnlySet<string> AllowedTools,\n    IReadOnlySet<string> Scopes,\n    int MaxTokenBudget,\n    int ContextCardinality,\n    long AvailableMemoryMb,\n    int? MaxLatencyMs,\n    string ComputeDeviceType,\n    string ComputeDeviceName,\n    string QuantizationLevel,\n    float ComputeThroughputTflops);

3.2 Kernel Startup State Machine

• SIR-003: Kernel startup sequence MUST be fixed to the following state machine:
• Inactive -> Initializing -> Governing -> Ready -> Executing
• SIR-004: Undefined transitions and transitions with unmet constraints MUST be fail-closed rejected, with exception throw and audit log emission.

public enum KernelState { Inactive, Initializing, Governing, Ready, Executing }\n\npublic interface IKernelStateMachine {\n    KernelState Current { get; }\n    bool CanTransition(KernelState next);\n    void Transition(KernelState next); // throw + emit audit event on invalid transition\n}

4. Governance / Constraints

4.1 Process Governance for Reasoning

Governance scope includes not only input and output, but also reasoning process itself.

• Step Constraint: Through governance policy, Thinking steps are capped to prevent model-side reinterpretation of design principles and hallucinated constraints.
• Audit of Abstract Pollution: In Replay Dump, if intermediate reasoning shows dependency-rule or responsibility-separation violations, resulting TrustLevel is significantly decayed.

4.2 Architecture Logical Audit

To reconcile intelligence non-determinism with system determinism, AIKernel.NET resolves the following paradoxes:

1. Deterministic replay freeze: During replay, bypass IModelVectorRouter and physically lock provider selection via LockedProviderInfo.
2. PDP reasoning isolation (Anti-Hallucinated Approval): Governance decisions (PDP) MUST NOT include LLM reasoning. Approval is always performed by deterministic code.
3. Semantic canonicalization: ROM MUST be canonicalized by ID sorting before persistence/signing so Git diff and semantic diff remain aligned.

5. Conclusion

The Semantic Context OS vision is the permanent north star constraining interface definitions, provider implementations, and future extensions in AIKernel.NET. The system is always Fail-Closed and never permits reasoning execution under integrity uncertainty.

6. Related Documents

• Principles of Information Category Separation
• Context Isolation Specification
• Attention Pollution Theory
• DI Composition and Pipeline Bootstrap
• Execution Contract Architecture
• PDP Guard Decision Plane
• Signed Prompt Governance Workflow
• Design Intent

7. Changelog

• v0.0.0 Draft

Changelog

• v0.0.0 / v0.0.0.0: Initial draft
• v0.0.1 (2026-05-06): Version upgrade aligned with documentation guidelines