Built Sam's latest memory-node inspiration into the live Command Center. The memory panel is now a larger Memory constellation workspace instead of a simple project graph. It mixes project nodes, connector nodes, and memory-source nodes, keeps the nodes source-linked, and adds visual layout controls for Macro, Mid, Micro, and Full.
Added source-linked memory signal data with three lanes: Recent activity, Stale, and Missing. The lanes include edit, recall, vectorize, and review actions so Sam can see where project memory is moving and where it is stale or unmapped.
Updated the data model with MemorySignalItem, added memorySignals to the dashboard contract, seeded source-linked mock records, extended tests, and added memory_signals to the schema spine. Updated docs/design/memory-connector-style-rules.md so this layout-control and signal-lane pattern is preserved.
Shipped commit: https://github.com/samaguiar1982-cpu/sail-command-center/commit/e981df9
npm test passed: 12 tests.npm run lint passed.npm run build passed.git diff --check passed./api/dashboard-data returned mode: live, live_error: null, and nine memory signals across recent, stale, and missing groups.artifacts/qa/2026-05-23/memory-constellation-live-1920x1080.png.artifacts/qa/2026-05-23/memory-constellation-live-mobile-390x844.png.Known dependency note: npm audit --audit-level=moderate still reports the existing Next/PostCSS advisory. The automated fix would downgrade Next to 9.3.3, so I did not apply it.
The requested memory-node inspiration has been implemented, verified visually and functionally, committed, pushed, and documented. No blocker remains for this design pass.
The best next build is to keep this richer constellation on the home screen, then build a full Project Memory module after the source registry and sync-run storage exist. That would make the recent, stale, and missing lanes real instead of mock-shaped.
Graph layout controls should remain visual-only until there is persistence for user preferences or graph layout. If they become functional, they should be backed by an audited source registry and should not silently modify local files or external sources.