diff --git a/agent/BACKLOG.md b/agent/BACKLOG.md
index 609fd18..778b87a 100644
--- a/agent/BACKLOG.md
+++ b/agent/BACKLOG.md
@@ -201,13 +201,7 @@ label `nix-kvm`), then an agent uncomments the workflow's `vm-checks`
 job: the `checks.*` VM suite + real toplevel/HM builds on every push
 (also upgrades item 14's bump gate from eval-only to the full suite).
 
-### 18. "nomarchy" control center + first-boot welcome `[big]`
-ROADMAP § control center. A single front-end over the common toggles on
-the same `nomarchy-theme-sync` surface, + a first-boot guided
-"pick your theme / essentials" flow. Needs a design pass (TUI vs GUI)
-→ write options into Decisions before implementing. Note: items 9–11
-(rollback menu, doctor, validation) are natural panels of it — design
-them as composable commands, not dead ends.
+
 
 ## LATER
 
@@ -273,8 +267,11 @@ decide.
   would flatten the aligned hand-formatting of ~33 files. Adopt or
   declare never?
 - **Docs site vs Markdown-in-repo** (from the docs-review item).
-- **Control center form factor:** TUI (gum/ratatui-style) vs GUI vs
-  "the rofi menu *is* the control center, just add a first-boot flow".
+- **Control center form factor (Item 18):** TUI vs GUI vs "rofi is the control center".
+  Requirements: Single front-end over `nomarchy-theme-sync`, first-boot "pick theme/essentials" flow, and composable panels for rollback (9), doctor (10), validation (11).
+  - *Option A (Rofi-native)*: The rofi menu *is* the control center. Add a `SUPER+C` root or `Control Center ›` submenu. First-boot is a script that chains rofi prompts. Pros: Reuses existing theming perfectly (no second theming pipeline), zero new deps. Cons: Rofi is a picker, not great for complex forms or multi-step back/next flows.
+  - *Option B (TUI - gum/ratatui)*: A floating terminal running a TUI. Pros: Excellent for guided flows and forms, fits the Nix hacker aesthetic, fast. Cons: Needs theming parity (terminal colors apply, but UI elements need tuning).
+  - *Option C (GUI - GTK4/WebKit)*: A dedicated GUI app. Pros: Premium feel, handles image previews (wallpapers/themes) easily. Cons: Directly conflicts with the "No second theming pipeline / No GTK4 launcher" non-goal unless extremely careful. High effort.
 - **zram swap:** faster under pressure and pairs with NOW#3, but it
   interacts with the hibernation-swapfile story (resume device/priority
   ordering) — adopt, adopt-with-hibernation-guard, or skip?
diff --git a/agent/JOURNAL.md b/agent/JOURNAL.md
index 6c1e021..85d9d9e 100644
--- a/agent/JOURNAL.md
+++ b/agent/JOURNAL.md
@@ -17,6 +17,13 @@ Template:
 
 ---
 
+## 2026-07-06 — control center design pass (iteration #48, item 18)
+- **Task:** BACKLOG NEXT#18 — control center form-factor design pass [big].
+- **Did:** moved item 18 entirely to the Decisions section; laid out the three form-factor options (Option A: rofi-native, Option B: TUI, Option C: GTK4/WebKit GUI) alongside their pros/cons and the specific requirements (first-boot flow, composable commands).
+- **Verified:** V0 (docs-only); `nix flake check --no-build` passed pre-commit.
+- **Pending:** the `[human]` decision on the form-factor.
+- **Next suggestion:** #14 (watch lock-bump CI) or #20 KVM runner [human]. If none actionable, triage PROPOSED or do a QA sweep.
+
 ## 2026-07-05 — display-profile workspace pins (iteration #47, item 15c)
 - **Task:** item 15 slice (c), the last one — per-profile workspace →
   output pinning. Item 15 deleted (a/b/c all shipped; V3s queued).