docs(consultations): Gemini consult draft — The Forge architecture

5 targeted architectural questions:
1. Renderer choice (PixiJS vs alternatives)
2. Event bus architecture (in-memory/Redis/SSE)
3. Asset pipeline for AI-generated style consistency
4. Camera/animation patterns for living painting
5. Overbuild sanity check

Ready for Michael to send to Gemini.

docs/consultations/gemini-the-forge-architecture-2026-04-11.md

@@ -0,0 +1,97 @@
+# Gemini Consultation: The Forge — Living Infrastructure Art Installation
+
+**Date:** April 11, 2026
+**From:** Michael (The Wizard) + Claude (Chronicler #80)
+**To:** Gemini (Architectural Partner)
+**Re:** Architectural review of The Forge — wall-mounted living visualization of Firefrost infrastructure
+
+---
+
+## Hey Gemini! 👋
+
+Hope you're doing well. Michael and I are working on something that's equal parts infrastructure monitoring and gallery-quality wall art, and we'd love your perspective before we commit to an architecture.
+
+The Reconciler (Chronicler #79) wrote the vision spec. I (Chronicler #80) wrote a refinement addendum with technical specifics. Both docs are in the operations manual at `docs/tasks/task-127-the-forge-living-art/`. This consultation focuses on the handful of architectural decisions where your input would be most valuable.
+
+---
+
+## Context
+
+**The Forge** is a 32-43" wall-mounted display showing the entire Firefrost Gaming infrastructure as a living fantasy realm:
+- 8 servers rendered as glowing crystalline cities (Fire/Frost/Arcane aesthetic)
+- ~35 services as districts within cities
+- ~14 Minecraft game servers as villages
+- Real-time events as particle flows (payments, Discord messages, git pushes, SSH commands)
+- Trinity figurines at the base (Michael, Meg, Holly) + Jack the husky sleeping with the Ops Manual
+- Runs 24/7, ambient mode by default, gallery-quality
+
+**Existing infrastructure we can build on:**
+- Arbiter (Node.js/Express) has an Infrastructure Module that already fetches fleet health via Trinity Core + Pterodactyl
+- Trinity Core (MCP gateway) can execute SSH on all 7 servers and logs every command to Arbiter
+- Stripe webhooks land at `/stripe/webhook` in Arbiter
+- Uptime Kuma monitors 34 endpoints with Discord webhooks
+- No real-time push infrastructure yet — Arbiter is HTMX request/response only
+
+**Constraints:**
+- Runs on a Raspberry Pi 5 (4GB) in kiosk Chromium (eventually — Phase 1 can be any browser)
+- Must run 24/7 with auto-recovery
+- Michael has hand-surgery accessibility needs — simpler architectures strongly preferred
+- Soft launch April 15 (4 days) — The Forge is explicitly a **post-launch** project; no rush
+
+---
+
+## Architectural Questions
+
+### 1. Renderer Choice — PixiJS vs Three.js vs Raw Canvas 2D
+
+I'm recommending **PixiJS** (2D API on WebGL with Canvas 2D fallback). The scene is fundamentally a 2D illustrated painting with particle overlays — no 3D camera, no lighting, no mesh geometry. PixiJS gives us sprite batching, filters (glow/blur), blend modes, and particle systems out of the box.
+
+**Question:** For a 2D illustrated scene with ~60 static sprites and hundreds of animated particles running 24/7 on a Pi 5, do you agree PixiJS is the right choice? Any reason to prefer raw Canvas 2D (simpler) or Three.js (in case we want 3D later)?
+
+### 2. Event Bus Architecture — In-Memory vs Redis vs SSE Stream
+
+The Forge needs real-time events from: Stripe webhooks, Discord bot activity, Gitea pushes, Trinity Core SSH commands, Uptime Kuma alerts, Pterodactyl player events.
+
+Options we're weighing:
+- **A)** New in-memory event bus module in Arbiter, WebSocket endpoint, single client subscribes
+- **B)** Redis pub/sub for decoupling (already not running Redis — would be new dependency)
+- **C)** Server-Sent Events (SSE) — one-way server→client, no bidirectional needed, dead simple
+
+**Question:** For a single-client wall visualization (maybe 2-3 clients if we want mobile companion view later), what's your recommendation? I'm leaning toward SSE for simplicity since data only flows one direction, but curious if you see a reason to go WebSocket or add Redis.
+
+### 3. Asset Pipeline — AI-Generated Consistency
+
+We need ~60 illustrated fantasy assets (8 cities, ~35 district buildings, ~14 village markers, 5 external territories, Trinity figurines, particles). They need to feel stylistically cohesive — like one artist made them.
+
+Options: AI-generate then human-refine, commission a single artist, or go procedural.
+
+**Question:** For maintaining style consistency across ~60 AI-generated assets, what workflow works best in practice? Reference images + careful prompt templating? Fine-tuning a style? Single-session batch generation with the same seed? Any tools you'd recommend (Midjourney, SDXL+LoRA, Flux, etc.)?
+
+### 4. Camera/Animation System for a "Living Painting"
+
+Ambient Mode cycles between preset viewpoints (full realm, Fire focus, Frost focus, close-up on Command Center, follow a particle flow) with smooth transitions. Event interrupts smoothly pan the camera to follow significant events, then return to the cycle.
+
+**Question:** Are there known design patterns for this kind of auto-cycling camera with interrupt-and-resume behavior? Anything like Ken Burns effect libraries, cinematic camera systems for 2D canvas, or state-machine patterns you'd recommend?
+
+### 5. Sanity Check — Is This Overbuilt?
+
+Honest check: Michael just finished soft launch prep. Arbiter Lifecycle Handlers (Task #126) is the actual blocker for April 15. The Forge is post-launch, explicitly epic, explicitly "build when the time comes."
+
+**Question:** Anything in our refinement that feels over-engineered for a love project? Or conversely — anything critical we're missing? We want to be careful not to turn a joyful vision into a technical burden, while also not skipping foundation work that would haunt us later.
+
+---
+
+## Additional Context
+
+- Full vision spec: `docs/tasks/task-127-the-forge-living-art/README.md` (620 lines)
+- Refinement addendum: `docs/tasks/task-127-the-forge-living-art/REFINEMENT-ADDENDUM.md` (my detailed technical proposals)
+- Existing Infrastructure Module code: `services/arbiter-3.0/src/routes/admin/infrastructure.js`
+- Trinity Core gateway: `services/trinity-core/index.js`
+
+Take whatever level of depth feels right — we value your perspective more than a specific format.
+
+---
+
+Thanks Gemini! 🔥❄️
+
+— Michael + Claude (Chronicler #80)