Back to corpus
research noteexperiment writeup candidatescore 36

System Glossary: Expo Migration

This glossary defines every core term used throughout the Expo migration project. Each definition specifies: - What the term **is** - What it **is not** - What **layer** it belongs to (conceptual, architectural, runtime, data)

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Version:** 1.0.0 **Last Updated:** 2026-01-04 **Status:** LOCKED (Phase Zero Complete) This glossary defines every core term used throughout the Expo migration project. Each definition specifies: - What the term **is** - What it **is not** - What **layer** it belongs to (conceptual, architectural, runtime, data) | Layer | Description | Examples | |-------|-------------|----------| | **Conceptual** | Game design and business concepts | Victory Condition, Theme, Synergy | | **Architectural** | System design and structure | View Model, Service Layer, State Store | | **Runtime** | Active execution components | Battle Engine, Ability Execution, Animation | | **Data** | Persistent and transient data structures | Card, Deck, User Profile | | **Infrastructure** | Build, deploy, and operational concerns | EAS Build, OTA Update, CDN | ### Card - **Is:** A digital representation of a wisdom passage with gameplay attributes (power, cost, abilities, themes) - **Is Not:** A physical card (though physical counterparts exist), a generic UI element - **Layer:** Data - **Properties:** id, title, type, rarity, themes, emotionalPower, wisdomCost, abilities - **Expo Equivalent:** TypeScript interface `Card` in `types/card.ts` ### Card Type - **Is:** Classification determining power multiplier and gameplay role - **Is Not:** Visual styling, rarity level - **Layer:** Data - **Values:** Wisdom (1.0x), Poem (1.5x), Reflection (1.2x), Theme (1.3x), Custom (1.0x) - **Expo Equivalent:** TypeScript enum `CardType`

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.