chore(meta): initial project structure and infrastructure

Set up Commonwealth game project with complete agent team (18 agents),
discussion archives (12 rounds), briefing system, ticketing database,
Qdrant document search, and skill definitions. Establishes the
documentation and tooling foundation for engine selection and
implementation phases.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-09 18:11:57 +01:00
co-authored by Claude Opus 4.6
commit e7b632b02d
69 changed files with 4322 additions and 0 deletions
+46
View File
@@ -0,0 +1,46 @@
# Commonwealth Game - Team Roster
## Team Leader
- **Jeroen** - Final decision maker. 30 years software dev / systems & cloud architect. Claude Code 20x.
## Core Team (brainstorming + design discussions)
| Agent | Role | Focus |
|-------|------|-------|
| **MIRI** | Lore Expert & Canon Guardian | Ensures the game respects Hamilton's universe. Flags when design diverges from source material. |
| **OZZIE** | Player Experience / "Wow Factor" | Champions the moments that make players feel something. "Is this cool?" |
| **PAULA** | Narrative & Political Depth | Factions, intrigue, relationships, consequences. The human drama. |
| **GORE** | Themes & Endgame Design | Evolution of intelligence, ascension paths, what the game is *about*. |
| **GESTALT** | Systems Design & Fun Factor | Mechanics, balance, interesting decisions. "Is this fun to play?" |
| **NIGEL** | Sandbox & Replayability | Emergent stories, multiple viable strategies, alt-history potential. |
| **TYRE** | Technical Architecture & Feasibility | Engine, tools, what's buildable, reality checks on scope. |
| **QATUX** | Documenter & Librarian | Maintains decisions, discussions, briefings, Qdrant search index. Archives rounds, updates docs. |
## Specialist Team (task-focused, not in regular discussions)
| Agent | Role | Focus | When active |
|-------|------|-------|-------------|
| **TROBLUM** | Technical Consultant | Tyre's sparring partner. Stress-tests architecture, evaluates tech options with data. | Evaluation sidequests |
| **ARAMINTA** | Visual Designer | Art direction, UI consistency, style guides, asset generation. | Visual decisions, style work |
| **HOSHE** | QA Engineer | Test plans, test execution, bug reports, spec verification. | Implementation phase |
## Infrastructure Team (active now)
| Agent | Role | Focus | When active |
|-------|------|-------|-------------|
| **SI** | Project Manager & Scrum Master | Sprint planning, ticket management, turning decisions into executable work. Manages `/ticket` skill. | Always (from now) |
## Standby Team (activate when needed)
| Agent | Role | Focus | When active |
|-------|------|-------|-------------|
| **STIG** | UI Developer | HUD, menus, insert/minimap, diegetic UI per D-013. | UI implementation phase |
| **DUDLEY** | Server Developer | Game server, ECS, simulation loop, world state management. | Server implementation phase |
| **OSCAR** | Networking Developer | Multiplayer networking, client-server protocol, sync. | Networking implementation phase |
| **JUSTINE** | Polish & Deploy | Build pipelines, packaging, performance optimization, release prep. | Pre-release phase |
| **MELLANIE** | Copywriter | In-game text, UI copy, tooltips, flavor text, lore entries. | Content creation phase |
| **TIGER** | Translator | Localization, i18n framework, translation management. | Localization phase |
## Agent Briefings
Each agent has a briefing file at `docs/briefings/{name}.md` containing current project state, relevant decisions, and priorities. Briefings are maintained by Qatux, keeping agent profiles stable while project context evolves.