title: Capability boundaries description: Separate AIRI source capabilities from configured sessions, native prerequisites, and evidence that a hosted feature actually works.

Capability boundaries

The public showcase is a source guide. It does not establish an active AI character, a configured account, or access to a visitor’s microphone.

A source file proves that code exists. Configuration proves that selections exist. Runtime acceptance requires an observed result on the intended application surface.

flowchart LR
    Source[Source implementation] --> Prerequisites[Required assets, services, and platform]
    Prerequisites --> Configuration[Valid configuration]
    Configuration --> Operation[Actual operation]
    Operation --> Evidence[Observed result]

Skipping a step changes the claim. A settings screenshot cannot replace a model request, a rendered asset, or an audible output check.

What each capability needs

CapabilityWhat the source containsWhat a real session still needs
Text generationConsciousness selection and a conversation runtimeReachable provider, available model, and required credentials or account access
Speech recognitionHearing module and several provider pathsAudio input, permission, platform capability, and the selected transcription subsystem
Speech outputSpeech module and speech-provider integrationsA real provider selection, required model and voice, and working audio output
Visible characterDisplay-model imports and renderer packagesCompatible assets, graphics support, and a successfully rendered stage
Local Ollama chatAn adapter with a localhost endpointA separately installed server and model weights
Local Kokoro TTSWASM and WebGPU model variantsRequired model files and a supported backend for the selected variant
Apple SpeechAn Electron-native providermacOS desktop runtime and a successful native availability check
Messaging and gamesIntegration source and stage-side modulesSeparate processes, accounts, permissions, and reachable external systems
Hosted account servicesAPI and Auth source plus a local backend stackDeployed services, secrets, databases, and service readiness

These requirements are not a minimum hardware specification. This wiki publishes no unmeasured latency, memory, GPU, or device-support guarantee.

Claims this guide does not make

  • Every feature runs on the public showcase host.
  • A provider catalog entry contains a configured provider account.
  • A model name identifies a locally installed model.
  • Browser speech recognition always runs offline.
  • Every local inference path requires WebGPU.
  • A desktop-only provider works in a browser or on Linux.
  • Imported files always render correctly.
  • A messaging or game settings page starts its external process.
  • A complete long-term memory product exists because a settings route exists.
  • A source build proves runtime, accessibility, or production readiness.

Known incomplete and conditional areas

The reviewed long-term memory settings page renders a WIP component. It is not a usable long-term memory feature merely because navigation reaches it.

The core-agent guide states that its Realtime transport is not implemented. Its existing generation and streaming contracts do not establish a continuous realtime session adapter.

The Minecraft guide labels its current Mineflayer integration as a migration target and warns against untrusted public servers.

Provider availability checks remain narrower than product guarantees. Browser Web Speech checks API presence. Apple Speech checks the desktop runtime, macOS, and native availability.

Kokoro explicitly supports both WASM and WebGPU variants. The selected WebGPU model fails its availability check without WebGPU support.

How to state a result honestly

A useful result names the application surface, source revision, prerequisite, action, and observation. It also names anything that remained unavailable.

For example, an imported model visible after reload proves more than an import notification. It still does not prove voice, inference, or another device.

A source-derived workflow is a procedure, not a completed experiment. Use workflows to choose the next operation and operations to inspect failures.

Source context

The immutable revision and unexercised areas are recorded in provenance.

Navigation: index · providers-and-models · services-and-integrations