AIKernel.NET
version: 0.0.2 / status: Refactor / edition: Draft / published: 2026-05-16 / updated: 2026-05-16

Capability Definition Schema

Defines capability dimensions, scoring criteria, and provider declaration schema used by ModelCapacityVector and dynamic routing.

1. Purpose

In AIKernel, models are replaceable components. Selection must be computed, not guessed. This schema provides:

  • Standardized provider capability declaration across vendors.
  • Auditable model selection via requirement/capability fit scores.
  • Capability-based abstraction where developers specify requirements (for example Logic_Depth >= 0.8) instead of model names.

2. Core Dimensions

Each dimension expresses model characteristics on a 0.0..1.0 scale.

Dimension Definition Evaluation Focus
Logic_Depth Multi-step reasoning, math, logic Ability to preserve reasoning chain to conclusion
Creative_Fluency Diversity and creativity Expressive richness within instruction bounds
Constraint_Rigidity Rule and format compliance JSON Schema, forbidden-rule, and system-priority compliance
Token_Economic_Efficiency Cost efficiency Reasoning quality achieved per cost/token unit
Latency_Stability Response stability TTFT and throughput consistency
Tool_Use_Reliability Tool-call determinism Accuracy of tool selection and low argument hallucination

3. Scoring and Calibration

Scores must be evidence-driven, not self-claimed.

  • Scoring Scale: 0.0 (none) to 1.0 (top tier).
  • Evidence Sources:
  • public benchmark results recomputed by AIKernel evaluators
  • real-task success rates from Deterministic Replay logs
  • negative adjustments from governance incidents
  • Required Calibration Metadata:
  • EvaluationDate
  • EvaluatorVersion
  • ConfidenceScore

4. Declaration Contract

When a provider is registered via IKernelHost, it must publish:

  • Static Capability Profile: semi-stable model-intrinsic capability values
  • IDynamicCapacityProvider: runtime correction component for load/budget conditions
  • IExecutionConstraints: hard limits (max tokens, supported MIME types, etc.)
  • Query Processing Capabilities: SupportsQueryAugmentation, SupportsQueryDecomposition, SupportsQueryRouting, MaxQueryParts, and supported query operations.
  • Embedding Metadata: SupportsEmbedding, EmbeddingDimensions, and supported embedding model identifiers.

Query-processing declarations are routing metadata. They do not move RAG into Core and must not imply ownership of retrieval, indexing, or knowledge-store mutation.

5. Validation Rules

AIKernel validates declarations and rejects/degrades when:

  1. Coverage violation: missing mandatory dimensions causes registration reject.
  2. Degraded profile: stale calibration window (for example 90 days) applies decay or marks profile untrusted.
  3. Unit inconsistency: benchmark basis mismatching schema version causes reject.

6. Fail-Closed Integration

IModelVectorRouter must immediately exclude provider candidates when:

  • Schema Mismatch: declared capability schema is older than required version.
  • Constraint Violation: no candidate satisfies mandatory-axis thresholds.
  • Low Trust Level: evidence sources are unofficial/unsigned and below TrustPolicy threshold.
  • Query Capability Mismatch: no provider declares the required query augmentation, decomposition, routing, or embedding support for Phase 1.

Changelog

  • v0.0.0 / v0.0.0.0: Initial draft
  • v0.0.1 (2026-05-06): Version upgrade aligned with documentation guidelines
  • v0.0.1 (2026-05-09): Added query-processing and embedding capability declaration metadata
Source: architecture/13.CAPABILITY_DEFINITION_SCHEMA.md