Cross-Repository Developer Guide v0.1.1.1

日本語

This guide is the first stop when a change crosses AIKernel repositories. It does not replace repository-specific docs. It explains where a responsibility belongs so developers do not reimplement logic in the wrong layer.

Reading Order

1. Read this guide to choose the owning repository.
2. Read Repository Alignment v0.1.1.1 for

versioning, package, and release-line rules.

3. Read Interface Canonicalization Roadmap v0.1.2

before promoting a local carrier into AIKernel.NET contracts.

4. Read Concept Elevation Guidelines

before adding a philosophical concept name.

5. Read the target repository's docs/README*.md for build and test commands.

Repository Ownership

Package and Release Rules

• The v0.1.1.1 line is NuGet-only.
• Do not create or publish PyPI packages for this local validation line.
• The next official release is the v0.1.2 canonical series. Treat v0.1.2 as the

next synchronized NuGet + PyPI package line.

• Local development package versions use 0.1.1.1-dev{build-number}.
• Keep existing public APIs stable. Add optional DTO properties or side-by-side

interfaces only when required.

• AIKernel.NET is the contract source of truth; implementation repositories

may carry local mirrors only as temporary extraction candidates.

CTG and Control Boundary

Decision Gate and Trajectory Gate logic belongs to Core.

Control may:

• normalize provider outputs into council votes,
• call Core CTG evaluators,
• attach diagnostics and retry intent outside GateInput,
• choose an execution pipeline from the returned decision envelope.

Control must not:

• count approvals,
• derive Ethos veto,
• create Gate decisions,
• copy Trajectory Gate halt logic,
• pass continuous values such as confidence, score, or risk into GateInput.

Providers, Wasm, Doom, and Tools must not emit GateDecisionKind, TrajectoryGateDecisionKind, or RejectReasonKind as sensor or perception outputs.

Sensor OS and Triadic Concepts

Sensor OS carriers use a map, not fixed arrays:

sensorInputs: { [sensorName: string]: SensorState }

The current v0.1.1.1 implementation keeps these carriers outside AIKernel.NET contracts so they can be consolidated in the v0.1.2 canonical update.

Legacy names Hodos, Zoe, and Topos were intermediate sensor labels. New code and docs should use the triadic model above unless preserving old metadata for compatibility.

Canonical concept flow:

Aisthesis -> Phantasia -> Nous -> Telos -> Ethos/Logos/Pathos\n  -> Kairos -> Kinesis/Praxis/Kratos -> Energeia -> Chronos

Promotion to AIKernel.NET v0.1.2

Before extracting a local implementation surface into AIKernel.NET:

• confirm it is provider-neutral and scenario-neutral,
• confirm it does not carry Gate decisions or reject reasons,
• confirm DTOs are immutable and collections are non-null,
• confirm public members have bilingual XML documentation,
• document old API to new API migration if any breaking change is proposed.

Current extraction candidates include:

• sensor input map carrier,
• spatial fusion vector carrier,
• retry intent carrier,
• sensor normalizer abstraction,
• spatial sensor fusion abstraction,
• retry intent resolver abstraction.

Validation Matrix

Run the smallest relevant command first:

dotnet test AIKernel.Core\AIKernel.Core.slnx -c Release --no-restore\ndotnet test AIKernel.Control\tests\AIKernel.Control.Tests\AIKernel.Control.Tests.csproj -c Release --no-restore\ndotnet test AIKernel.Providers\tests\Perception\AIKernel.Providers.Perception.Tests\AIKernel.Providers.Perception.Tests.csproj -c Release --no-restore\ndotnet test AIKernel.Wasm\AIKernel.Wasm.slnx -c Release --no-restore\ndotnet test AIKernel.Doom\AIKernel.Doom.slnx -c Release --no-restore

For browser-facing changes, also run JS syntax checks and sync the development site:

node --check AIKernel.Doom\src\DoomWeb\wwwroot\js\doom.js\nWebSite\script\sync_dev_wwwroot.ps1

When using browser automation, verify that no Node.js debug process remains after the check.

Common Mistakes

• Putting a shared contract into an implementation repository.
• Letting Control reproduce Core Gate logic.
• Letting Providers become SDK wrappers instead of capability adapters.
• Letting Wasm depend on Providers perception substrate directly.
• Letting Doom-specific event names leak into Wasm or Providers.
• Using philosophical names on DTOs, mappers, adapters, serializers, or provider

implementation classes.

• Reintroducing PyPI packaging into the v0.1.1.1 validation line instead of

preparing it for the v0.1.2 canonical release line.