← all documents · raw markdown · 5 KB

KAI Dual-World Platform Goal

| | |
|---|---|
| Status | VISION LOCK + Phase 0/1 slice |
| Owner intent | Account → Avatar (you) with public/private data; 2D Oracle dashboard + 3D KAIVERSE are the same world at different speeds/dimensions (PS Home / No Man's Sky feel). |
| Related | Guest feed/shorts/subscribe, plan-tiers, KAIVERSE quest design, social-agents |

---

Core idea (owner words, cleaned)

1. Avatar = you (not an autonomous AI)

On create account / Me:

This is not an autonomous fleet bot. It is their body/persona in the platform.

2. Two dimensions, one world

| Dimension | What it is | Movement feel |
|-----------|------------|---------------|
| 2D — Oracle dashboard | Menus, Feed, Shorts, Chat, Me, Subscribe | God / teleport — tab jumps = instant travel across the map of your home planet / network |
| 3D — KAIVERSE | Fly/walk cosmos, realtime presence | Embodied — fly, walk, land; slower, spatial, "really there" |

Same places exist in both forms (easter eggs can link 2D spot ↔ 3D coordinates).

3. What you do in 2D shows in 3D

4. Content pillars (both dimensions over time)

Missions, quests, adventures, Battle Royale (cosmos), shops, houses, places (area of sight), easter eggs 2D+3D, multiplayer social.

Quest spine already designed: KAIVERSE-QUEST-SYSTEM-DESIGN.md (errors→quests; public = explorer tier).

5. Home planet metaphor

---

Mapping to current code

| Concept | Today | Gap |
|---------|--------|-----|
| Avatar identity | /api/social-agents + DiceBear | Still labeled "agent"; needs isAvatar / primary + public/private split |
| Profile public | /api/me/profile bio/etc. | Needs explicit public vs private schema |
| Private notes | tenant notes | Keep private-only |
| KAIVERSE body | Fleet planets / hard-part places | User avatar mesh/presence not wired as "you" |
| 2D teleport | View switches | Not yet mapped to place ids |
| 3D realtime | kaiverse.js flight | Must not break first-person feel; avatar additive |
| Quests | Design doc only | Not fully playable loop |

---

Phased build

Phase 0 — Language + privacy model (now)

Phase 1 — Presence bridge

Phase 2 — 3D avatar body

Phase 3 — Place graph

Phase 4 — Play systems

---

Non-goals (immediate)

---

Success (Phase 0–1)

1. User understands Avatar = me (public/private).

2. Create/list shows primary avatar clearly.

3. Presence API records current 2D "place" (view).

4. Doc + API ready for 3D body attach later.

Phase 2–3 shipped (2026-07-16)