Architecture: How to wire MCP decision intelligence into Vitto's runtime c...

Documentation for Sessions

🏗️ Architecture: How to wire MCP decision intelligence into Vitto's runtime c...

Date: 2026-03-24
Time: 15:17:30 UTC
Session: gspace1-263.4
Agent: backend
Confidence: 93%
Status: ✅ Documented


📋 Decision Context

Question:

How to wire MCP decision intelligence into Vitto's runtime context (Intelligence Bridge)?

Task: Not specified


🎯 Decision Made

Chosen:

5-gap fix: (1) Inject learning intelligence into context-assembly.service.ts via BackendAiClientService.getLearningIntelligence(), (2) Fix pattern mining dedup with SHA-256 deterministic hash + upsert, (3) Add domains[] and audience to Decision schema for categorization, (4) Include golden decisions in getPyramidContext response, (5) Sync agent specializations to sub-agent definitions via daily cron.

Options Considered:

  1. Full rewrite of learning pipeline (too risky, existing infrastructure works)
  2. Vector search for similar decisions only (misses patterns and golden decisions)
  3. Frontend-only intelligence display (doesn't help Vitto's runtime decisions)

💭 Reasoning

12K+ MCP decisions exist in ai-api but Vitto never reads them at runtime. The only bridge was a daily cron syncing patterns to sub-agent knowledge docs (text, not structured). Root causes: (1) context-assembly.service.ts never called getLearningIntelligence(), (2) pattern mining dedup used charCode sum + Date.now() producing non-deterministic IDs, (3) decisions had no domain categorization so filtering was impossible, (4) golden decisions (curated high-quality examples) weren't included in the pyramid context, (5) agent specializations from decision history never reached sub-agent definitions. Each fix is independent and additive — no breaking changes.


📁 Files Involved


🔗 Related


Auto-generated by MCP Smart Consolidation