Back to corpus
architecturetechnical paper candidatescore 54

Meaning Full Power - Game Mechanics Architecture

This document provides a comprehensive breakdown of all game mechanics, their interfaces, dependencies, and how they interconnect. Use this as a reference when developing or debugging individual components.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This document provides a comprehensive breakdown of all game mechanics, their interfaces, dependencies, and how they interconnect. Use this as a reference when developing or debugging individual components. 1. [System Overview](#1-system-overview) 2. [Core Data Models](#2-core-data-models) 3. [Battle Engine](#3-battle-engine) 4. [Theme System](#4-theme-system) 5. [Ability Engine](#5-ability-engine) 6. [Deck System](#6-deck-system) 7. [Persistence Layer](#7-persistence-layer) 8. [Victory Conditions](#8-victory-conditions) 9. [AI Opponent System](#9-ai-opponent-system) 10. [Game Rules Reference](#10-game-rules-reference) 11. [Component Dependency Graph](#11-component-dependency-graph) 12. [Implementation Checklist](#12-implementation-checklist) **Key Computed Properties:** - `effectivePower`: Base power × type multiplier - `allThemes`: Primary + secondary themes - `qrCodeURL`: Deep link for physical card scanning | Type | Power Multiplier | Count | Description | |------|-----------------|-------|-------------| | Wisdom | 1.0x | ~85 | Prose passages | | Poem | 1.5x | 14 | Rare, powerful | | Reflection | 1.2x | 28 | Interactive questions | | Theme | 1.3x | 12 | Pure elemental cards | | Custom | 1.0x | Unlimited | AI-generated | | Rarity | Drop Rate | Border Color | Max Copies/Deck | |--------|-----------|--------------|-----------------| | Common | 60% | Gray #6B7280 | 3 | | Uncommon | 25% | Silver #C0C0C0 | 3 | | Rare | 10% | Gold #FFD700 | 2 | | Epic | 4% | Purple #9B59B6 | 2 | | Legendary | 1% | Orange #FF6B35 | 1 |

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

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.