diff --git a/docs/code-bridge/requests/REQ-2026-04-12-phase11-prerequisites.md b/docs/code-bridge/requests/REQ-2026-04-12-phase11-prerequisites.md
new file mode 100644
index 0000000..b24b32c
--- /dev/null
+++ b/docs/code-bridge/requests/REQ-2026-04-12-phase11-prerequisites.md
@@ -0,0 +1,19 @@
+# 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
+
+1. **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)
+2. **Existing Arbiter DB schema** — Can you dump the current table list from arbiter_db so I know what's already there? (`\dt` output)
+3. **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?
+4. **Arbiter .env current state** — What env vars does Arbiter already have? (So I don't overwrite anything when adding the new ones)
+5. **Discord role + channel setup** — Has the "ModpackChecker Customer" role been created on the Firefrost Discord? Does the bot have permission to assign roles?
+6. **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?