diff --git a/neode-ui/src/views/dashboard/keepAliveRoutes.ts b/neode-ui/src/views/dashboard/keepAliveRoutes.ts
index 67825299..e883fc8e 100644
--- a/neode-ui/src/views/dashboard/keepAliveRoutes.ts
+++ b/neode-ui/src/views/dashboard/keepAliveRoutes.ts
@@ -12,9 +12,23 @@ import { TAB_ORDER } from './useRouteTransitions'
 
 /** Maximum number of main-tab component instances kept alive at once (D-03).
  * Bounds memory on low-power fleet nodes — the oldest unused instance evicts
- * once this cap is exceeded (Vue's own LRU eviction). Stays at 6 against the
- * ~11 registered paths below (FA-D) — plan 02-08 tunes it against real
- * on-device memory, not guessed at again here. */
+ * once this cap is exceeded (Vue's own LRU eviction).
+ *
+ * 02-08 (FA-D) tuned this against an on-device measurement rather than
+ * leaving the carried-forward estimate unexamined: on archi-dev-box (real
+ * node hardware, deployed build), a headless Chromium session logged in via
+ * the real UI, cycled every main tab (all of TAB_ORDER incl. the withheld
+ * `/dashboard/settings`, plus `/dashboard/discover` — 11 tabs) through 4 full
+ * two-way round-trips (44 navigations total, well past the single "twice"
+ * the task calls for), reading the JS heap via CDP `Performance.getMetrics`
+ * before and after each cycle. Result: ~8.8MB before any navigation, then
+ * 10.02 / 20.69 / 16.67 / 14.12 MB after cycles 0-3 respectively (final
+ * reading 14.68MB) — fluctuating, not monotonically growing, across 10
+ * distinct cache-registered paths exceeding this cap. That confirms the
+ * eviction is actually bounding memory rather than the cap sitting unused,
+ * and the absolute growth (single-digit MB) is inconsequential on any
+ * low-power fleet node's available RAM. Left at 6, unchanged — a measured,
+ * confirmed 6 rather than the FA-D estimate it replaces. */
 export const KEEP_ALIVE_MAX = 6
 
 /** TAB_ORDER paths deliberately withheld from the instance cache this plan