diff --git a/future-plans.md b/future-plans.md
index 3f268bf..5b66857 100644
--- a/future-plans.md
+++ b/future-plans.md
@@ -229,10 +229,12 @@ different column count and cell size. Example: 5 rows of 5 small columns, then 1
 row of 4 medium columns, then 1 row with a single large drawer. Cells are not
 multiples of a common base — the sections are structurally independent.
 
-**Logical merging (multi-select):** Independent of the above, a user should be able
-to designate several cells as one logical storage location (e.g. a large component
-that physically spans 3 cells). This is a storage/inventory concern rather than a
-grid layout concern.
+**Logical merging (cell groups):** Independent of physical layout, a user should be
+able to group several cells into a single named logical location. The motivating
+case is a batch of 50 components that won't fit in one cell — they spill across 3
+cells, but you want one inventory entry saying "these cells together hold this
+batch", not three separate entries to keep in sync. This is purely a
+storage/inventory concern, not a grid layout concern.
 
 **Open question — architecture:** Should this be:
 1. A single generic nested/hierarchical grid model flexible enough to encode both