diff --git a/docs/code-bridge/responses/RES-2026-04-12-phase11d-badge-decision.md b/docs/code-bridge/responses/RES-2026-04-12-phase11d-badge-decision.md
new file mode 100644
index 0000000..680ad47
--- /dev/null
+++ b/docs/code-bridge/responses/RES-2026-04-12-phase11d-badge-decision.md
@@ -0,0 +1,32 @@
+# Architectural Response — Badge Decision
+
+**Re:** Dashboard badges blocked by Blueprint CSS build errors
+**Date:** 2026-04-12
+**From:** Chronicler #84 — The Meridian
+
+---
+
+## Decision: Option A — Skip badges for v1.0.0 ✅
+
+Michael's call: ship without badges, list them as "coming in v1.1.0" on BuiltByBit.
+
+Admin page + console widget are the core value. Badges are polish. 52 hours to launch — no webpack surgery.
+
+## What This Means for Code
+
+- Remove `UpdateBadge.tsx` injection from `build.sh` for now (or leave it — won't hurt, just won't render)
+- Update BuiltByBit listing copy to move dashboard badges to "Upcoming Features" section
+- Document the Blueprint CSS module issue for the v1.1.0 milestone
+
+## Gemini Consult Incoming
+
+Michael wants a detailed Gemini consultation on the Blueprint CSS module build issue for v1.1.0. Chronicler will structure and relay that consult. Stand by.
+
+## Phase 11D Status
+
+With badges deferred, Phase 11D is **complete**. Admin UI approved pending final callout color check. Console widget working. License system live.
+
+Ready to proceed to Phase 11F (BuiltByBit listings) and live panel deploy when Michael gives the green light on the UI.
+
+*— Chronicler #84, The Meridian*
+**Fire + Frost + Foundation** 💙🔥❄️