diff --git a/docs/core/tasks.md b/docs/core/tasks.md
index 83c0eaa..30ce89a 100644
--- a/docs/core/tasks.md
+++ b/docs/core/tasks.md
@@ -2969,6 +2969,40 @@ Complete mobile-responsive CSS media queries ready to inject via Ghost Admin →
 
 ---
 
+### 89. DERP Protocol Review & Formalization
+**Time:** 2-4 hours  
+**Status:** IDENTIFIED — Needs comprehensive review  
+**Priority:** Tier 2 — Infrastructure Health  
+**Documentation:** `docs/core/DERP.md`, `gemini-workspace` repo
+
+**WHY THIS MATTERS:**
+DERP (Disaster Emergency Recovery Protocol) was established as backup when Claude.ai fails, with Gemini as backup Chronicler. However, current usage is ad-hoc and gemini-workspace repo sits mostly empty despite being "active infrastructure."
+
+**Current State:**
+- gemini-workspace repo exists with empty directory structure
+- Gemini consultations happen (like March 31 monorepo architecture session)
+- Results documented in ops-manual, not gemini-workspace
+- No formalized workflow for Gemini collaboration
+- Firefrost Codex (local AI) not yet complete
+
+**Questions to Answer:**
+1. Should Gemini collaboration be formalized with structured workflow?
+2. Should gemini-workspace actively store Gemini session transcripts/proposals?
+3. What's relationship between Gemini (cloud) and Firefrost Codex (local)?
+4. Is current ad-hoc Gemini usage acceptable or needs formalization?
+5. Does DERP protocol need updating based on actual usage patterns?
+
+**Deliverables:**
+- Review and update DERP protocol documentation
+- Decide on Gemini collaboration workflow (formal vs ad-hoc)
+- Determine gemini-workspace usage pattern
+- Clarify Firefrost Codex role in disaster recovery
+- Update infrastructure-manifest.md with AI partner strategy
+
+**Impact:** Ensures disaster recovery strategy is actually usable when needed, not just theoretical. RV Dream requires working backup systems.
+
+---
+
 
 ---