🏗️ Architecture: How should Vitto's autonomy be configured — global setting v...

Date: 2026-02-07
Time: 20:34:06 UTC
Session: gspace1-99.4
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should Vitto's autonomy be configured — global setting vs hierarchical overrides?

Task: Not specified

🎯 Decision Made

Chosen:

Hierarchical overrides: handoff > session > global, with 4 levels (OBSERVE, SUGGEST, DIRECT, AUTONOMOUS)

Options Considered:

• No alternatives documented

💭 Reasoning

Handoff-level overrides let a specific critical task auto-execute while the default requires approval. Session overrides let a developer switch autonomy for their session without affecting others. Sub-session fallback (session-99.2 → session-99) avoids config duplication. Config persisted in MongoDB autonomy-config collection, cached in memory for fast shouldProceed checks.

📁 Files Involved

• apis/backend-vitto-api/src/app/engine/autonomy.service.ts
• apis/backend-vitto-api/src/app/mind/schemas/autonomy-config.schema.ts

🔗 Related

• Decision ID: dev_1770496446788_igf2jcz
• Session: 99
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation