title: Source provenance description: Record AIRI’s upstream revision, source hierarchy, corrected documentation drift, local adaptation boundary, and unexercised prerequisites.

Source provenance

This wiki describes a specific AIRI source snapshot. It separates upstream implementation, local showcase work, and runtime evidence.

Upstream identity

Field	Recorded source context
Repository	moeru-ai/airi
Upstream revision	`3da3cf815490b40521e24b22020954e7959d79b4`
Root package version	`0.12.0-beta.5`
Root package-manager pin	`pnpm@11.24.0`
Source review date	2026-09-15
Local checkout used for authoring	`/home/loca/dev/airi`
Wiki source scope	`/home/loca/dev/wikis/airi/content`

The checkout’s origin identifies https://github.com/moeru-ai/airi. Its feat/airi-showcase branch reference supplied the upstream base revision during authoring.

The immutable public package.json also resolved during source research. The source links throughout this wiki use that exact revision, not the moving main branch.

Evidence labels

Label	Meaning in this guide
Source-backed	The cited implementation or manifest contains the described behavior or declaration
Upstream guide	A checked-out README describes a workflow or boundary, without this wiki claiming a fresh runtime replay
Owner-reported	The integration owner supplied a host observation outside the wiki author’s source-reading scope
Not exercised	No corresponding runtime, provider, device, or deployment operation occurred during wiki authoring

flowchart TD
    Revision[Pinned upstream revision] --> Implementation[Implementation and manifests]
    Revision --> Guides[Upstream guides]
    Implementation --> Claims[Source-backed wiki claims]
    Guides --> Claims
    Local[Local showcase changes] --> Separate[Separate adaptation evidence]
    Host[Owner-reported host observation] --> Runtime[Runtime context only]
    Claims --> Reader[Reader sees scope and limits]
    Separate --> Reader
    Runtime --> Reader

Source map

architecture traces application manifests, web route generation, the chat store, and package ownership.
modules traces character stores, provider state, and shared settings pages.
setup traces root scripts, application scripts, tool metadata, and asset downloads.
workflows traces settings routes, selection behavior, and model import boundaries.
providers-and-models traces portable definitions, saved configuration, local adapters, and search paths.
character-and-audio traces character prompts, display assets, renderer boundaries, and audio policies.
services-and-integrations traces backend composition, edge routing, server-channel code, and integration guides.
operations traces persistence, failure categories, service-worker behavior, and service readiness guidance.
capability-boundaries records incomplete or conditional capabilities without converting them into hosted claims.

Each page provides exact repository paths and immutable source links near its conclusion.

Documentation differences kept visible

Implementation and manifests take precedence over summaries when their claims differ.

Topic	Difference found	Treatment in this wiki
Provider-store path	The root agent guide names `stores/providers.ts`, but the current stores are `stores/providers/config.ts` and `stores/providers/provider.ts`	Cite the current files
Backend port exposure	The backend README describes only Caddy exposure, but Compose also publishes PostgreSQL and Redis on loopback	List all three actual host bindings
Node versions	`.tool-versions` names Node `26.7.0`, while contributor guidance says Node `23+`	Label both as repository metadata
Showcase host runtime	The owner reports Node `v22.23.1` with Corepack pnpm `11.24.0`	Record the host choice separately, without a version-switch claim
Memory navigation	The long-term memory route renders `WIP`	Do not claim a complete memory feature

The host did not switch Node versions. This record does not establish that every upstream workspace supports the host’s selected version.

Local showcase versus upstream

The local showcase work belongs to apps/stage-web/src/pages/index.vue and the application shell under apps/stage-web/src/App.vue.

Those working-tree changes are a local adaptation. The pinned upstream links show the base source, not an immutable publication of the local changes.

This wiki does not assign a fabricated commit or public source URL to that adaptation. Its final source revision and deployment evidence belong to the integration record.

The showcase and this wiki are reader-facing surfaces. Their descriptions do not stand in for provider or native-device acceptance.

What authoring did not establish

Wiki authoring did not run builds, linters, deployment changes, browser acceptance, model inference, microphone capture, audio playback, or external bots.

No provider credentials, hardware capabilities, account readiness, or production health results are inferred from source presence. See capability-boundaries.

Primary references

package.json: identity, license declaration, and commands.
.tool-versions: repository tool metadata.
.github/CONTRIBUTING.md: contributor guidance.
server/README.md and server/docker-compose.yaml: documented and executable backend context.

Navigation: index · architecture · operations

Project AIRI

Explorer