Skip to content

EchoSpire Official Documentation

This directory is the canonical documentation set for EchoSpire: Portals.

It exists to replace fragmented design notes with a smaller, stable set of documents that define the project for design, engineering, content, and future production work.

These documents are derived from the current repository GDD and the GPT-5.4 documentation set under docs/gpt54. Other model outputs in the repository are not part of the official canon unless they are promoted into this directory.

If you want the short list of immediate priorities, start with Current Next Steps.

Document Set

  • Current Next Steps: the short list of immediate follow-up work that should happen next.
  • Document Governance: what is canonical, how conflicts are resolved, and how this set should be maintained.
  • World And Lore: the setting, historical timeline, factions, leaders, and narrative tone.
  • Gameplay Reference: the player-facing structure of the game, classes, factions, run loop, and content rules.
  • Ludo Import Brief: a compact product and UX summary formatted for Ludo-style ideation and import workflows.
  • Realm Framework: unstable attached realms, realm-wide passive effects, and the single-realm quest model built from sectors and breach-sites.
  • Rift Types And Variables: the official rift taxonomy, current node families, and the authoring variables each rift type should expose.
  • Rules Glossary: the official terminology and mechanical definitions for shared, class, and faction systems.
  • Hero Progression And Difficulty: the level 10 hero model, specialization choices, and environment scaling rules.
  • Campaign And Conflict Framework: the authored quest structure, faction storyline model, and rival hero system.
  • Opening Story Quest Build Guide: the recommended canonical prologue sequence and quest scaffolding.
  • AI Systems And Agents: where deterministic gameplay AI, constrained generative AI, and operational agents each belong.
  • Simulation And Rival Hero AI: the official model for simulator policies, enemy and boss selectors, and rival hero gameplay AI.
  • Live-Site AI Agent: the operational agent design for session diagnostics, incident triage, and balance recommendations.
  • Pseudo-Production And Deployment: the recommended first external testing environment, hosted surfaces, and on-demand deployment flow.
  • Hosted Early-Dev Deployment: the lowest-friction hosted setup using Cloudflare Pages, Render, Neon, and Upstash.
  • Hosted Early-Dev Runbook: the step-by-step operator checklist for bringing the low-cost tester environment online.
  • Technical Architecture: the system design, platform choices, core technical principles, and project boundaries.
  • WPF MVP Kickoff: the Windows-first MVP client direction, architecture, and build order for the first paid preview.
  • WPF UX Flow Map: the current screen flow, player-facing shell rule, and canonical asset intake structure for the WPF client.
  • Unity Client Kickoff: the later migration target for a post-proof presentation upgrade once the product is validated.
  • Ludo Asset Prompts: the stored prompt library for later Unity UI and faction asset generation.
  • Effect Pipeline And Modular Deployment: the official direction for code-based effects, trigger sub-pipelines, module loading, and UX event emission.
  • Production Roadmap: current state, priority gaps, and the recommended production sequence.
  • Master TODO: the cross-discipline backlog of missing work.

Intended Use

Use this folder as the first stop for:

  • Immediate priority questions
  • Lore and setting questions
  • Gameplay terminology and rules questions
  • Ludo import, product brief, and UX concept summary questions
  • Hero progression and scaling questions
  • Realm identity and realm-passive questions
  • Rift-type and node-variable questions
  • Campaign, quest, and rival hero questions
  • AI architecture, simulation policy, and live-site diagnostics questions
  • pseudo-production hosting, deployment topology, and release-flow questions
  • low-cost hosted deployment and early external testing setup questions
  • step-by-step hosted rollout and operator execution questions
  • WPF MVP kickoff, screen-flow, and Windows-first paid-preview questions
  • WPF UX flow, screen stub, and asset intake questions
  • Unity migration-target, screen-flow, and later integration-boundary questions
  • reusable Ludo prompt and later Unity visual asset generation questions
  • Effect pipeline, triggers, and UX event questions
  • Architecture and implementation guidance
  • Production planning and milestone definition

Use the GPT-5.4 prototype docs as source material and historical context. Use the GDD for deeper raw detail. Use this folder for the current official answer.