🏗️ Architecture: Session 176 Phase B: How to make Vitto aware of user's curre...

Date: 2026-03-05
Time: 17:10:10 UTC
Session: gspace1-178.4
Agent: angular
Confidence: 93%
Status: ✅ Documented

📋 Decision Context

Question:

Session 176 Phase B: How to make Vitto aware of user's current page context and executable actions?

Task: Not specified

🎯 Decision Made

Chosen:

Wired pageContext through 4 layers: frontend VittoPageContextRegistry → HTTP body field → VittoEngineService → ContextAssemblyService system prompt. Registered VittoSettings (was missing). Added actions to MemoryManager, ChannelManager, WorkflowBuilder, SkillMarketplace.

Options Considered:

• No alternatives documented

💭 Reasoning

Alternatives: (a) tool-call parameter — requires frontend changes to intercept each message, (b) system prompt injection — simplest, existing contextEnrichment computed signal already produces the text, (c) separate context API — over-engineered. Chose system prompt injection: zero frontend changes beyond existing registry, backend only needs to accept and append the string. 4/5 components already registered with VittoPageContextRegistry, only VittoSettings was missing. Actions added: searchMemory, filterByType, connectChannel, testChannel, installSkill, createWorkflow, saveWorkflow, executeWorkflow, updateSetting, resetToDefaults.

📁 Files Involved

• No files specified

🔗 Related

• Decision ID: dev_1772730610384_9yv0byc
• Session: 178
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation