OPERATIONS¶
Specs for the running pieces of SectorWars 2102 — the AI assistant, the two web UIs, the real-time/multi-regional infrastructure, and i18n. These describe the target design.
Index¶
| Doc | Scope |
|---|---|
aria.md |
ARIA AI companion: design, security model |
admin-ui.md |
Admin web app (services/admin-ui/) — tech stack, structure, features |
player-client.md |
Player web app (services/player-client/) — tech stack, structure, features |
realtime.md |
WebSocket layer, presence, broadcast, room management |
multi-regional.md |
Central Nexus + per-region containers |
i18n.md |
Translation pipeline (5 languages) and the workflow for adding more |
monetization.md |
Subscription tiers (Galactic Citizen, Region Owner), PayPal flow, billing lifecycle |
bang-integration.md |
sw2102-bang world-generator contract: input config, output JSON, gameserver consumption |
ui-flows.md |
Player-client and admin-ui journeys: page-to-page transitions, key affordances |
retention.md |
Engagement metrics, inactivity decay, at-risk signals, re-engagement campaigns |
Sibling areas¶
../ARCHITECTURE/— service topology, deployment, dev environment../DATA_MODELS/— schema and entity definitions../FEATURES/— gameplay design (what these systems are for) and the only place implementation status is tracked
Conventions¶
OPERATIONS docs describe the intended design. Whether each piece is currently shipped, partial, or buggy is tracked inline in the matching FEATURES/ file.