1.5 KiB
1.5 KiB
Architectural Request
Date: 2026-04-12 Topic: Phase 11 Prerequisites — Need credentials and env values before Code can begin
1. Current State
Phase 11 spec is archived and understood. Code is ready to begin building the licensing system (database migration, Arbiter API routes, Blueprint extension changes).
2. The Blocker
Cannot start implementation without infrastructure values that only the Chronicler (via Command Center access) can provide.
3. Questions for Chronicler
- PostgreSQL credentials — What are the connection details for arbiter_db on Command Center? (host, port, user, password — or confirm it's 127.0.0.1 with the existing Arbiter DB user)
- Existing Arbiter DB schema — Can you dump the current table list from arbiter_db so I know what's already there? (
\dtoutput) - BuiltByBit resource IDs — Have the two listings (Standard / Professional) been created yet? If so, what are BBB_STANDARD_RESOURCE_ID and BBB_PRO_RESOURCE_ID? If not, should Code proceed with placeholder values?
- Arbiter .env current state — What env vars does Arbiter already have? (So I don't overwrite anything when adding the new ones)
- Discord role + channel setup — Has the "ModpackChecker Customer" role been created on the Firefrost Discord? Does the bot have permission to assign roles?
- Deployment readiness — Once Code writes the migration SQL and API routes, should I commit and push for Chronicler to deploy? Or is there a staging step first?