“Answer” Thread Summary
Source: apps/stps/deploy_n_v2/v3/raw/answer.md.
Highlights
- Session rooms: treat sessions as literal rooms—entering a session reconfigures layout, tools, AI context, and auto-links everything you create.
- Session memory: sessions store what was learned/decided/created and can form chains (
continues_from,continues_to). - Universal blocks: every text field uses the same BlockEditor where blocks can embed nodes, run live queries, host AI output, or transform into other node types. Slash commands (
/signal,/task,/ai,/session, etc.) unlock power features. - Session kinds: broad list (learning, translation, glossary, ideation, research, writing, planning, design, coding, extraction, analysis, meeting, standup, focus, reading, journaling, etc.) so the system can tailor layouts/tools per context.
Keep this close when designing session-specific UIs or extending the universal block system.