diff --git a/DESIGN.md b/DESIGN.md
index cea5149..5f1ffc9 100644
--- a/DESIGN.md
+++ b/DESIGN.md
@@ -267,19 +267,19 @@ That's a substantial shader inventory.  Each requires bit-exact M1 gate against
 
 ## 9. Open questions
 
-1. **Intra prediction strategy:** GPU wavefront (~187 dispatches, more complex) vs CPU speculative (simpler, slower).  Plan: wavefront in Phase 1; revisit if it's the perf bottleneck.
+1. **Intra prediction strategy:** GPU wavefront (~187 dispatches, more complex) vs CPU speculative (simpler, slower).  Plan: wavefront in Phase 1; revisit if it's the perf bottleneck. [x]
 
-2. **libavcodec intercept granularity:** macroblock-level (substitution-arc evolution) vs slice-level (cleaner rewrite).  Plan: macroblock-level for Phase 1; consider slice-level later if buffer accumulation overhead is non-trivial.
+2. **libavcodec intercept granularity:** macroblock-level (substitution-arc evolution) vs slice-level (cleaner rewrite).  Plan: macroblock-level for Phase 1; consider slice-level later if buffer accumulation overhead is non-trivial. [x]
 
-3. **Shader parameterization:** 16 qpel variants as 16 shaders, or one parameterized shader with switch on mc_position?  V3D's compiler might inline-optimize either; needs measurement.
+3. **Shader parameterization:** 16 qpel variants as 16 shaders, or one parameterized shader with switch on mc_position?  V3D's compiler might inline-optimize either; needs measurement. [x] Measurement it is.
 
-4. **DPB allocation:** Vulkan-native VkImage with dmabuf export, vs CPU-allocated dma_buf imported into Vulkan.  Affects V4L2 integration story.  Plan: Vulkan-native with `VK_KHR_external_memory_dma_buf` export; daedalus-v4l2 daemon imports.
+4. **DPB allocation:** Vulkan-native VkImage with dmabuf export, vs CPU-allocated dma_buf imported into Vulkan.  Affects V4L2 integration story.  Plan: Vulkan-native with `VK_KHR_external_memory_dma_buf` export; daedalus-v4l2 daemon imports. [x]
 
-5. **Daemon integration shape:** does daedalus-decoder ship as a static library the daemon links, or as a separate process the daemon talks to?  Library, almost certainly — process boundary would multiply IPC cost.
+5. **Daemon integration shape:** does daedalus-decoder ship as a static library the daemon links, or as a separate process the daemon talks to?  Library, almost certainly — process boundary would multiply IPC cost. [x] library.
 
-6. **Build dependency on daedalus-fourier:** as a CMake `find_package`, or vendored?  `find_package`, pinned to a tagged release.  daedalus-fourier becomes the "kernel pack" upstream library.
+6. **Build dependency on daedalus-fourier:** as a CMake `find_package`, or vendored?  `find_package`, pinned to a tagged release.  daedalus-fourier becomes the "kernel pack" upstream library. [x] Yes.
 
-7. **Out-of-scope for daedalus-decoder (firmly):** VP9, AV1, HEVC (Pi 5 has rpi-hevc-dec for that), 10-bit, interlaced, FMO/ASO.
+7. **Out-of-scope for daedalus-decoder (firmly):** HEVC (Pi 5 has rpi-hevc-dec for that), 10-bit, interlaced, FMO/ASO.
 
 ---