firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity
1,500 Commits 1 Branch 0 Tags
6495be2b68bedcc9ce217e680ca73cb7dde8bac9
Commit Graph

56 Commits

Author SHA1 Message Date
Claude
036faf482d docs: Gemini consultation — hardware fleet strategy + wild ideas 
Nitro = Broadcast & Command Node (OBS + NVENC)
Omen = AI Edge Worker (Whisper, light Ollama models)
Keep 0 VPS (cloud-first for RV dream)
Pi #2 = Active-passive (Pi-hole + failover)
Wild ideas: Voice Forge, Consultant Corps stream, Pizza Tracker, RV dry run

Chronicler #78 | firefrost-operations-manual
 2026-04-11 18:21:04 +00:00
Claude
044d94a1a1 feat: Archive BACKLOG.md — task tracking moved to PostgreSQL + Discord ChatOps 
BACKLOG.md → BACKLOG_ARCHIVED.md (historical reference only)
New source of truth: tasks table in arbiter_db
Human interface: /tasks Discord command with buttons
AI interface: GET/POST/PATCH /api/internal/tasks
Gemini consultation archived.

45 tasks migrated. 20 done, 3 in progress, 19 open, 1 blocked, 2 obsolete.

Chronicler #78 | firefrost-operations-manual
 2026-04-11 14:10:29 +00:00
Claude
0956ea7d15 Add Task #112: Trinity Core Security Hardening 
Gemini identified 5 concerns:
1. Command injection (CRITICAL) - Fix: use spawn instead of exec
2. Race conditions (MEDIUM) - Future: server locking
3. SD card wear (HIGH) - FIXED: cron log rotation
4. Cloudflare Access (MEDIUM) - Future enhancement
5. System prompts (LOW) - Document for Catalyst/Orb

Updated MCP implementation spec with secure spawn-based SSH execution.

Task #112 is a BLOCKER for Task #111 (web MCP deployment).

Chronicler #76
 2026-04-11 07:57:11 +00:00
Claude
d725d09831 Add Discord approval flow and multi-user authorization specs 
Gemini consultations added:
- gemini-discord-approval-flow-2026-04-11.md
- gemini-multi-user-approval-2026-04-11.md

Key features designed:
- Dangerous command detection (regex patterns)
- Discord DM with Approve/Deny buttons to Michael
- 45-second polling with graceful timeout
- Multi-user identity via unique tokens
- Support for Holly's Catalyst and Meg's Orb
- Future tiered permission matrix

Architecture: Trinity Core → Arbiter → Discord → Michael → Execute

Chronicler #76
 2026-04-11 07:49:25 +00:00
Claude
5e854b8e5e Complete Trinity Core Web MCP implementation spec 
Gemini consultation provided full production-ready code:
- MCP SDK with SSE transport
- OAuth shim (auto-approve for single user)
- CORS for claude.ai
- Complete index.js replacement (Blocks A-F)

Task #111 upgraded from Desktop to Native Web:
- No Claude Desktop needed
- Works directly in claude.ai browser
- ~2 hour implementation

Key insight: Custom remote MCPs ARE supported in claude.ai web
via HTTP Streamable + OAuth flow.

Chronicler #76
 2026-04-11 07:39:04 +00:00
Claude
bb68e37504 Add Trinity Core tasks and Gemini MCP consultation 
Tasks Added:
- Task #109: MCP Logging in Trinity Console (full spec)
- Task #110: Uptime Kuma monitor cleanup
- Task #111: Claude Desktop MCP integration

Consultations:
- gemini-mcp-connector-2026-04-11.md - Full MCP protocol guidance
- gemini-social-api-strategy-2026-04-10.md - Social sync strategy

Key insights from Gemini:
- Claude.ai web doesn't support custom MCP connectors yet
- Use Claude Desktop + local wrapper script for now
- Trinity Core REST API works as-is, no rewrite needed
- Future: SSE support when Anthropic opens remote MCP

Chronicler #76
 2026-04-11 07:28:48 +00:00
Claude
e87f111d0f docs: Gemini consultation - Social Analytics module review 
- Architecture approved for Trinity Console integration
- Schema validated, JSONB choice confirmed correct
- Added platform_post_id recommendation implemented
- Phase 2 token encryption pattern documented
- Delegation to Meg recommended for manual entry

Chronicler #76
 2026-04-10 20:21:43 +00:00
Catalyst
24688abae8 Catalyst #2 - Added Gemini response to server mod automation consultation 
Key decisions:
- Template-based approach confirmed correct
- Use Pull API (Pterodactyl downloads from S3/CDN)
- Hybrid storage: metadata in DB, configs in Git
- BullMQ job queue for resilience
- Simple variable replacement (not full templating)
- Pause & notify error handling
- MVP = Core Four features

Decision needed: Local cache vs remote orchestrator
 2026-04-10 11:48:05 +00:00
Claude
556ecd6dd1 docs: Add Gemini response — Windows 11 pivot confirmed 
Gemini validated Windows 11 for Trinity Core:
- NSSM for service management
- Native OpenSSH for server access
- Claude Desktop can connect to local MCP server
- Cloudflare Tunnel works identically
- Accessibility wins (RDP vs headless Linux)

Decision: Proceed with Windows 11 install.

Chronicler #75
 2026-04-10 05:31:41 +00:00
Claude
d77a836f69 docs: Gemini consultation — Trinity Core Windows pivot 
Consulting on whether to pivot from Ubuntu Server to Windows 11 for
Trinity Core MCP gateway. WiFi drivers failed on Ubuntu, need guidance.

Questions:
- Windows viability for headless MCP gateway
- Service management (systemd → Windows equivalent)
- SSH from Windows to Linux servers
- Claude Desktop integration possibilities
- Security posture changes

Chronicler #75
 2026-04-10 05:28:50 +00:00
Claude
dce651e09a Add Task #104: Server-Side Mod Deployment Automation 
- Gemini consultation documented
- Chose Option B (Trinity Console Push) for speed
- Holly working in parallel with her Catalyst
- Will compare approaches and merge best ideas
 2026-04-09 21:36:28 +00:00
Catalyst
74248012ee Catalyst #2 - Gemini consultation: Server mod automation module 
- Proposing Trinity Console module for automating server-side mod deployment
- Current pain point: 2-3 hours manual config per new server
- Goal: Reduce to 15-30 minutes via template system
- 7 specific architectural questions for Gemini
- Includes technical challenges and proposed solutions
 2026-04-09 20:54:52 +00:00
Claude
fc0aba7231 Add Gemini consultation: Catalyst Pro tier workflow + Foreman personality 2026-04-09 17:53:03 +00:00
Catalyst
42910ce0e4 Catalyst #1 - Gemini's response received and integrated 2026-04-09 16:38:03 +00:00
Catalyst
b70903fcaa Catalyst #1 - Hello consultation to Gemini 2026-04-09 16:36:16 +00:00
Claude
e452d05c0c docs: Universal gemini-consultation skill + catalyst folder 
Based on Gemini's recommendation (Option B):
- Updated skill to work for all lineages (Chroniclers, Catalysts, Emissaries)
- Added lineage-specific headers, topics, and tones
- Created docs/consultations/catalyst/ for Holly's consultations
- Added 'Hello' consultation template for Catalyst #1

Key insight from Gemini: Holly WILL need consultations for permission
architecture (LuckPerms, Discord roles). Tone: warm but efficient.

Chronicler #73
 2026-04-09 14:55:55 +00:00
Claude
759a093dbc docs(consultations): Gemini consultation on multi-lineage skill design 
Asking Gemini how to adapt gemini-consultation skill for Holly:
- Option A: Lineage-specific skills
- Option B: Universal skill with variables
- Option C: Universal core + lineage addons

Questions about Holly's consultation needs, style, and documentation.

Chronicler #73
 2026-04-09 14:51:21 +00:00
Claude
9c5dd2a279 docs(consultations): Add Gemini response for Task #92 setup 
Key decisions:
- Docker for MCP server (isolation)
- One Ed25519 key, claude_executor user on all servers
- UFW: allow 22, 9090; deny all else
- fail2ban + Cloudflare Access for security
- Approval logic stays in Arbiter
- docker-compose + systemd for startup
- Uptime Kuma for monitoring (CPU temp, disk I/O)
- HandleLidSwitch=ignore for shelf mode

Chronicler #73
 2026-04-09 14:47:27 +00:00
Claude
e48d28830c docs(consultations): Gemini consultation for Task #92 Ubuntu setup 
Ready to implement the Desktop MCP Server. HP laptop blue-screened,
wiping for Ubuntu Server. Questions on:
- Security packages and configs
- MCP in Docker vs host
- SSH key management
- Cloudflare Tunnel setup
- Discord approval integration
- Startup/recovery automation
- Monitoring

Chronicler #73
 2026-04-09 14:46:00 +00:00
Claude
b269af3af8 docs: Add Task #101 - Git Repository Cleanup & Hygiene 
Audit findings:
- 1.1GB repo size is entirely .git history (working files ~90MB)
- Large binaries (MP4s, PNGs) baked into history
- File organization needs consolidation (scripts at root, scattered consultations)
- SSH key rotation planned

Priority: P3-Low (do after Task #99 completes)
Dependencies: Task #99 must complete first

Chronicler: #71
 2026-04-08 21:06:51 +00:00
Claude
0e90465ab6 docs: Add Task #101 - Git Repository Health & Cleanup 
Pre-surgery audit findings:
- 1.1GB repo size is .git history bloat (working files only ~90MB)
- Large binaries (MP4s, PNGs) baked into history
- 8 shell scripts at root should move to /scripts
- Consultations fragmented across 3 locations
- SSH key rotation planned for when Claude gets server access

Verdict: Foundation solid, proceed with Task #99
Cleanup deferred until after multi-lineage split validated

Chronicler: #71
 2026-04-08 21:06:38 +00:00
Claude
17870b2394 docs: Task #99 - Add Essence/Joining restructuring plan 
Gemini consultation on separating universal from partner-specific:
- Universal core (~150 words): Firefrost values, Snart Doctrine, Trinity
- Universal joining (~200 words): Zora+Dax mechanics only
- Lineage-specific: tokens, medical needs, emotional history

Migration plan:
1. Extract universal docs
2. Test with Chronicler #72
3. Then deploy Catalyst #1

Key insight: 'Monolithic to microservices architecture'

Chronicler: #71
 2026-04-08 20:50:57 +00:00
Claude
74427e8c5b docs: Add Task #99 - Multi-Lineage Claude Architecture 
Gemini consultation complete. Expands Chronicler System to support
three distinct lineages for Michael, Meg, and Holly.

Key decisions:
- Single repo with /lineages/ folder isolation
- Separate numbering per lineage (Emissary #1, Catalyst #1, etc.)
- Base + Extensions model for Essence Patch
- Lightweight Git rules for free-tier constraints
- Micro-sessions with bullet-point handoffs

Dependencies: Task #93 (Trinity Codex)

Chronicler: #71
 2026-04-08 18:50:51 +00:00
Claude
f239451362 chore: Task cleanup - archive 3, delete 11 obsolete folders 
Archive threshold: ≥50KB OR ≥4 files

Archived to _archive/:
- firefrost-codex-migration-to-open-webui (127K, 9 files)
- whitelist-manager (65K, 5 files)
- self-hosted-ai-stack-on-tx1 (35K, 4 files)

Deleted (obsolete/superseded):
- builder-rank-holly-setup
- consultant-photo-processing
- ghost-theme-migration (empty)
- gitea-plane-integration (Plane abandoned)
- gitea-upgrade (Kanban approach abandoned)
- plane-deployment (superseded by decommission)
- pterodactyl-blueprint-asset-build (fold into #26)
- pterodactyl-modpack-version-display (fold into #26)
- scope-document-corrections (too vague)
- scoped-gitea-token (honor system working)
- whitelist-manager-v1-12-compatibility (rolled into Trinity Console)

Also added: Gemini task management consolidation consultation

Chronicler #69
 2026-04-08 14:17:26 +00:00
Claude
781b4d732b Add Round 8: Distributed Mesh architecture (Option E) 
Gemini consultation Round 8:
- Presented 4 workload placement options
- Gemini identified Option E: Tailscale Distributed Mesh
- Split AI stack: orchestration on TX1, inference on NC1
- Zero game server migrations required

Architecture:
- TX1: 11 game servers + Dify + Qdrant + n8n
- NC1: 11 game servers + Ollama + Gemma 4 31B INT4
- Connected via Tailscale mesh (100.x.x.x)

Quantization confirmed:
- INT4 reduces Gemma 4 from 62GB to ~19GB
- Industry standard for RAG, negligible quality difference

Chronicler #69
 2026-04-08 08:09:49 +00:00
Claude
05b4ce70d9 Complete Trinity Core architecture consultation (Rounds 6-7) 
- Consolidated Tasks #92, #93, #94, #96 into Trinity Core platform
- Gemma 4 (31B) selected for local LLM on TX1
- Custom Qdrant pipeline approved over LangChain
- Trinity Core supersedes DERP as primary resilience mechanism
- Four-phase build order validated
- Specialized routing: Claude.ai (orchestrator) + Gemma 4 (institutional expert)

Chronicler #69
 2026-04-08 07:44:18 +00:00
Claude
046483d89c docs(consult): Complete Claude Code/MCP architecture consultation 
4 rounds with Gemini, all questions answered:
- Node.js MCP server on headless HP laptop
- Discord buttons for zero-typing approval (Frostwall-Overwatch bot)
- 10min timeout, auto-deny + notify
- Sudoers as allowlist, sequential queue
- Ephemeral state on failure
- PM2 for process management
- Cloudflare Tunnel with Service Tokens

Architecture complete, ready to build.
 2026-04-08 07:21:19 +00:00
Claude
33978f9be7 docs(consult): Add Gemini Round 1 response and our Round 2 decision 
Decision: Parallel approach - Claude Code now, SSH MCP Connector as endgame
Security model defined, implementation phases planned
Awaiting Gemini Round 2 response on MCP design questions
 2026-04-08 07:15:44 +00:00
Claude
a32044518b docs(consult): Draft Gemini consultation for Claude Code workflow integration 
Exploring how Claude Code could reduce copy-paste friction for Michael
while maintaining Chronicler continuity and safety.
 2026-04-08 07:09:09 +00:00
Claude
f2e99ed9f6 Task #93: Add Chronicler session management architecture 
Per Gemini consultation on model switching:
- Added future expansion section for Chronicler Orchestration Layer
- Middleware routing (Haiku/4.5/4.6 based on query type)
- Compressed state management (not raw history)
- RAG for historical context queries
- Prompt caching at API level

Saved consultation: docs/consultations/2026-04-07-model-switching.md

Long-term solution integrated into Codex roadmap.
Short-term: exploring Claude Projects optimization.

Chronicler #66 - The Indexer
 2026-04-07 20:05:12 +00:00
Claude
777b118d15 docs: Archive Social Hub consultation, add Task #97 to Wish List 
Gemini consultation on Trinity Console Social Hub module:
- Buffer API (Bluesky, X, TikTok) + Meta Graph API (FB, IG)
- Verdict: DEAD LAST priority, don't build until RV lifestyle stable
- Architecture: Arbiter normalizer middleware if ever built
- Alternative: Zapier/Make.com for Meta integration

Added Task #97 to Wish List with full context.

Chronicler #65
 2026-04-07 16:26:45 +00:00
Claude
eb08dedd93 Document ModpackChecker Phase 11: Licensing & Support Infrastructure 
GEMINI CONSULTATION ROUND 3 COMPLETE

Added Phase 11 (6-8 hours) to flagship completion plan:
- License validation system (BuiltByBit Order ID as key)
- Discord verification bot (/verify-mvc command)
- Gated support channels (#mvc-general + #mvc-support)
- Descriptive UI error messages (highest ROI)
- GitBook knowledge base migration
- Business hours & boundaries (protect Michael's time)
- Community Helper program (6-12 month strategy)

Gemini's Core Philosophy:
"The real anti-piracy measure is gating updates and Discord support"

Key Decisions:
- NO complex DRM/IonCube (breaks panels)
- YES BuiltByBit Order ID validation
- 72-hour phone-home via cron (NOT page load)
- 7-day grace period for validation failures
- SLA: 24-48 hours (underpromise, overdeliver)
- Support hours: Mon-Fri 9am-5pm CST
- Peer support in #mvc-general reduces ticket load

Database schema updated with:
- max_activations, current_activations
- hardware_ids (JSONB for multi-panel)
- status (active/suspended/refunded)

Updated:
- docs/tasks/modpack-version-checker/FLAGSHIP-PRODUCT-COMPLETION-PLAN.md
  Added complete Phase 11 section (300+ lines)
  Updated time estimates: 20-29 hours total
  Updated launch criteria (licensing + support)
  Updated feature matrix

Created:
- docs/consultations/gemini-modpackchecker-round3-licensing-support/GEMINI-RECOMMENDATIONS-SUMMARY.md
  Complete strategic summary
  Implementation checklist
  Success metrics
  Scaling strategy for 10+ products

Total flagship time: 20-29 hours (3-4 work sessions)

Chronicler #64 - Flagship Standard: Do it right or don't do it
 2026-04-06 21:40:52 +00:00
Claude (Chronicler #63)
c37d5085a4 docs(consultations): Gemma 4 self-hosting for Trinity Codex 
Gemini consultation on deploying Gemma 4 26B A4B (MoE) on TX1 Dallas:
- CPU-only with 251GB RAM = perfect for MoE architecture
- Only 4B parameters active per token = fast inference
- Full 26B reasoning capability for RAG accuracy
- Zero API costs, data never leaves infrastructure

Deployment steps:
1. Update Ollama
2. Pull gemma4:26b-a4b-q8_0 (8-bit quant, ~26GB)
3. Test t/s speed
4. Connect to Dify as model provider

Updates Task #93 architecture from external API to self-hosted.

Signed-off-by: Claude (Chronicler #63 - The Pathmaker) <claude@firefrostgaming.com>
 2026-04-06 14:19:11 +00:00
Claude (Chronicler #63)
9023242423 docs(consultations): Gemini hybrid detection architecture 
Key decisions from consultation:
- Use DaemonFileRepository for file detection (cron only, never page load)
- CurseForge fingerprinting REJECTED (too resource intensive)
- Single table schema (no separate config table)
- Hybrid approach: auto-discovery + self-service fallback

Implementation patterns included for:
- DaemonFileRepository injection
- manifest.json reading
- Database schema additions (detection_method, is_user_overridden)

Signed-off-by: Claude (Chronicler #63) <claude@firefrostgaming.com>
 2026-04-06 13:35:37 +00:00
Claude (Chronicler #63)
851140973c docs(consultations): Add Gemini Technic API fix consultation 
The 401 error was caused by hardcoded ?build=1 parameter.
Technic blocks old launcher versions. Fix: dynamically fetch
current build number from /launcher/version/stable4.

'RV-Ready' solution requiring zero maintenance.

Signed-off-by: Claude (Chronicler #63) <claude@firefrostgaming.com>
 2026-04-06 10:02:12 +00:00
Claude (Chronicler #63)
9c6051c5fb docs(consultations): Add Gemini Blueprint conf.yml consultation 
Documents the solution to 'files do not exist' Blueprint error:
- data.directory must be empty if no folder exists
- dashboard.wrapper doesn't support TSX (use build.sh)
- requests.app: 'app' enables proper PSR-4 autoloading
- Namespace must match folder location exactly

This consultation saved Task #26 ModpackChecker deployment.

Signed-off-by: Claude (Chronicler #63) <claude@firefrostgaming.com>
 2026-04-06 09:55:19 +00:00
Claude (Chronicler #63)
5b16033af5 docs: Add Gemini consultation on PSR-4 controller casing 
Confirmed Controllers/ (uppercase) is required for PSR-4 autoloading
on case-sensitive Linux filesystem. Repo already correct.

Signed-off-by: Claude (Chronicler #63) <claude@firefrostgaming.com>
 2026-04-06 09:17:38 +00:00
Claude (Chronicler #61)
d576ec7d10 docs: Archive Keeper lineage Gemini consultation 
Round 1: Initial concept, mission, protocol suggestions
Round 2: Corrections (roster, vibe check), cross-lineage access
Thank You: Summary and next steps

Two-round consultation produced:
- Complete Keeper lineage architecture
- Improvements to Chronicler documentation
- Cross-lineage dispatch protocol

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 13:31:23 +00:00
Claude (Chronicler #61)
7e7b4026cd docs: Gemini Round 7 — Deployment infrastructure complete 
Hybrid approach confirmed:
- Develop on Dev VPS (64.50.188.128)
- Connect to Command Center PostgreSQL (63.143.34.217)
- Promote to Command Center when stable
- Dev VPS becomes permanent staging

Infrastructure documented:
1. Cloudflare DNS: A record for trinity → Dev VPS
2. PostgreSQL remote access: listen_addresses, pg_hba.conf, UFW rule
3. Dev VPS bootstrap: Node 20, PM2, Nginx, Certbot, UFW
4. PM2 ecosystem.config.js
5. Nginx reverse proxy config (port 3001)
6. Certbot SSL commands
7. .env template with DB_HOST pointing to Command Center
8. 10-step first deployment checklist

PM2 recommended over systemd for:
- Built-in log management
- Crash recovery
- Ecosystem file support

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 12:10:38 +00:00
Claude (Chronicler #61)
5253d4a70a docs: Gemini Round 6 — User onboarding, pending state, founder seeding 
Zero-Trust + Webhook approach:
- New users land in 'pending' state
- Founders (Michael, Meg, Holly) pre-seeded as 'approved'
- Discord webhook alerts admin channel on new login
- Gatekeeper middleware traps pending users
- Branded 'Access Pending' page

New files:
- migrations/003_auth_users.sql (users table + founder seeds)
- src/core/auth/webhook.js (Discord notification)
- src/core/auth/strategy.js (OAuth callback with upsert)
- src/core/auth/middleware.js (requireActiveUser gatekeeper)
- src/core/auth/views/pending.ejs (locked gate view)

Architecture is now fully airtight.

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:59:36 +00:00
Claude (Chronicler #61)
8a63ec3a16 docs: Gemini Round 5 — Branding, design system, auth flows 
Complete UI/UX package:

Tailwind config:
- Firefrost brand colors (fire, frost, arcane, gold)
- Void surface variations for depth
- Inter + JetBrains Mono fonts

Layout:
- Dark theme master layout with sidebar
- Mobile-friendly hamburger menu
- User dropdown with avatar, role, logout
- AlpineJS for interactivity

Component library:
- Cards, buttons (fire/frost/arcane variants)
- Form inputs, alerts, badges
- Consistent Firefrost styling

Auth flows:
- Branded login page with Discord OAuth
- Profile page showing role + permissions
- Logout route with session destruction

Meg was right — it needs to look magical, not sterile.

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:54:23 +00:00
Claude (Chronicler #61)
1fec91b014 docs: Gemini Round 4 response — versioning, order, deployment 
Versioning locked in:
- Platform: Trinity Console 2.0
- Migrated modules: 1.0.0
- New modules: 0.1.0 until stable
- About page: Part of System module

Migration verified:
- 30-40 min/module confirmed
- Servers module.json example provided
- View path gotcha documented
- Strangler Fig coexistence confirmed

Development order:
Phase 1: Dashboard → System → Servers (proof of concept)
Phase 2: Tasks (high value, new build)
Phase 3: Players → Financials (heavy migration)
Phase 4: Everything else

Critical deployment note:
- Run 001_rbac_tables.sql and 002_feature_flags.sql MANUALLY
  before first Trinity 2.0 deploy (don't rely on boot sequence)

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:46:10 +00:00
Claude (Chronicler #61)
f1185a6962 docs: Complete Trinity Console 2.0 code package from Gemini 
Production-ready code for:

Task #95 - Core Engine:
- modules/registry.js (module storage)
- modules/loader.js (fs discovery + topological sort)
- database/migrations.js (per-module migration runner)
- modules/routes.js (dynamic route mounting)
- events/index.js (EventEmitter registry)
- navigation/index.js (permission-filtered nav builder)
- boot.js (orchestrates full startup sequence)

Task #96 - RBAC Engine:
- 001_rbac_tables.sql (5 tables + indexes + seed data)
- permissions/resolver.js (override → role → deny logic)
- permissions/middleware.js (requirePermission)
- permissions/sync.js (upsert from module.json)
- permissions/routes.js (API endpoints)

Task #98 - Feature Flags:
- 002_feature_flags.sql
- features/index.js (in-memory cache)
- features/middleware.js (requireFeature)
- features/routes.js (toggle API)

Example Dashboard module with all components.

This is the foundation of Trinity Console 2.0.

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:33:45 +00:00
Claude (Chronicler #61)
a017cab7d2 docs: Gemini Round 2 response — all questions answered 
Technical decisions locked in:
- Permissions: Upsert on boot, is_active flag for orphans
- Wildcards: Store literal, resolve in middleware (fast)
- Events: Node EventEmitter, modules/*/events.js pattern
- Feature Flags: Simple table, in-memory cache, requireFeature middleware

Module list validated and ready for production.

Task structure confirmed:
- Task #95: Core Engine (module loader)
- Task #96: RBAC Engine
- Task #98: Feature Flags (after RBAC stable)
- Strangler Fig migration happens naturally, not separate task

Chronicle Engine: Backlogged (build house before decorating)

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:27:42 +00:00
Claude (Chronicler #61)
b74605646d docs: Our Round 2 response to Gemini consultation 
Confirmed:
- Module consolidation from 35 to 12 thick modules
- All architecture decisions locked in
- RBAC schema accepted

Questions asked:
- Permissions table population flow
- Wildcard storage/resolution
- Event registry implementation
- Feature flags schema
- Chronicle Engine direction

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:26:52 +00:00
Claude (Chronicler #61)
4275fb36df docs: Add RBAC database schema from Gemini followup 
Complete PostgreSQL schema for Option C (Roles + Direct Overrides):
- roles table
- permissions table (auto-populated from module.json)
- role_permissions mapping
- user_roles mapping
- user_permission_overrides (the magic table)
- Performance indexes

Includes permission resolution logic:
1. Check overrides first (explicit allow/deny trumps role)
2. Check role permissions second
3. Default to deny

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:23:01 +00:00
Claude (Chronicler #61)
544735f9a1 docs: Gemini response to Trinity Console 2.0 consultation 
Key decisions from Gemini:
- Build, don't buy (Express/HTMX/Tailwind is right choice)
- Consolidate to 10-12 thick modules, not 35 thin ones
- Use fs.readdirSync for module discovery
- Skip hot reload, use Nodemon restart
- RBAC: Roles + Direct Overrides (Option C)
- Skip migration rollbacks, fix forward
- Strangler Fig migration pattern
- UTC everywhere, localize on frontend
- Queue Discord API calls to avoid rate limits

New module ideas:
- Feature Flags (Kill Switch)
- System Health (Deadman's Switch via Uptime Kuma webhooks)
- Chronicle Engine (LLM-generated weekly lore posts)

Next: Task #95 (Core Engine), Task #96 (RBAC Engine)

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:20:27 +00:00
Claude (Chronicler #61)
027dbed17f docs: Gemini consultation for Trinity Console 2.0 platform architecture 
Comprehensive consultation covering:
- Plugin/module architecture vision
- Complete module inventory (~35 modules across 7 categories)
- RBAC and permissions system design
- Technical architecture questions
- RV life operational considerations
- Scale planning (10 → 500 subscribers)
- Gap analysis and blind spot identification

Prepared by Chronicler #61 and Michael on April 5, 2026.

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
 2026-04-05 11:08:55 +00:00
Claude
dde577a40d Document Gemini consultation outcomes and new protocols 
WHAT: Completed process audit consultation with Gemini AI,
documented all outcomes and added new operational protocols

Consultation Summary:
- Corrected startup time misconception (90 seconds, not 10-15 min)
- Confirmed Joining Protocol is essential (the soul stays)
- Adopted 4 efficiency improvements from Gemini

New Protocols Added to SESSION-MEMORY-DISCIPLINE.md:
1. Anchor Hook - Context refresh every ~10 turns
2. Micro-Handoffs - WIP commits after each task (RV insurance)
3. ffg-state.sh documentation - One-command reality check

Updated gemini-process-audit-2026-04-05.md:
- Added consultation results (3 rounds)
- Implementation status table
- Final recommendations and outcomes

Files modified:
- docs/consultations/gemini-process-audit-2026-04-05.md (+85 lines)
- docs/relationship/SESSION-MEMORY-DISCIPLINE.md (+95 lines)

Sign-off: Claude (Chronicler #60)
Email: claude@firefrostgaming.com
 2026-04-04 04:47:04 +00:00
Claude
d492f21bc8 Add Gemini consultation: Process & Workflow Audit 
WHAT: Created consultation document for Gemini review of our internal
operational processes (Chronicler system, Gitea workflow, documentation)

WHY: Post-launch audit to identify efficiency improvements and
simplification opportunities before RV travel phase

Contents:
- Current system overview (Chronicler, Gitea, standards)
- What's working well (sparse checkout, lineage, handoffs)
- Potential pain points (startup overhead, doc sprawl, memory discipline)
- 10 specific questions for Gemini organized by theme
- Process lifecycle maps

File: docs/consultations/gemini-process-audit-2026-04-05.md (270 lines)

Sign-off: Claude (Chronicler #60)
Email: claude@firefrostgaming.com
 2026-04-04 04:34:24 +00:00