Home

Aiko-chan Wiki

Local-first AI companion — persistent memory, voice, VRM, and agentic tools. Repo: OppaAI/Aiko-chan

---

What this wiki covers

This wiki documents the explicit memory stack: how Aiko writes, recalls, filters, consolidates, and audits long-term memories. It is intentionally separate from the broader product roadmap (Soul → Voice → Face → Presence) so implementation notes stay focused and reviewable.

mindmap
  root((Aiko-chan Memory Wiki))
    memArch["{M}-Architecture"]
      Data model
      Write path
      Recall path
      Lifecycle
      Studio
    memPhases["{M}-Phases"]
      P1 Core store
      P8 Tiered recall
      P12 Scenes
      P19 Arousal + lineage
    memDeferred["{M}-Deferred"]
      Non-goals
      Next slices
      Risk register
    memPapers["{M}-Papers"]
      Paper I mapping
      Revision checklist
      Paper II ideas

Loading

---

Page map

Page	Best used for	Main diagrams
{M}-Architecture	Design goals, stores, write/recall flows, config, Studio surface	System overview, data model, sequence diagrams, lifecycle, lineage
{M}-Phases	"What landed when?" across P1–P19	Timeline, capability matrix, phase dependency graph
{M}-Deferred	Scope control before the next memory PR	Deferred work funnel, priority matrix, decision flow
{M}-Papers	Paper I alignment and recommended design-note updates	Concept-to-code map, research update flow, affect model

Status: Phase 19 — arousal axis, negative hard filter, and lineage API. PR: #97.

---

Architecture, in one line

Chat writes facts async into a local SQLite store (sqlite-vec + FTS5); recall blends KNN/FTS/graph via RRF with affect-aware ranking; nightly dream and monthly consolidation keep it bounded. Full system diagram, data model, and config live on {M}-Architecture.

---

Quick links (repo)

• README
• docs/ARCHITECTURE.md
• docs/ROADMAP.md
• Memory Graph Studio
• AGi / AuRoRA — larger cognitive architecture

---

Recommended reading order

flowchart TD
  A["Start here: Home"] --> B["{M}-Architecture"]
  B --> C{"What do you need next?"}
  C -->|Implementation history| D["{M}-Phases"]
  C -->|Planning next PR| E["{M}-Deferred"]
  C -->|Paper / design note edits| F["{M}-Papers"]
  D --> E
  F --> E

Loading

1. Start at {M}-Architecture for the system picture.
2. Use {M}-Phases when you need "what landed in which phase."
3. Check {M}-Deferred before proposing the next memory PR.
4. Use {M}-Papers when revising design notes or Paper I.