DecisionQueue: DEC-2026-005 for Qonto Governed Assistant Phase 1

Bundles the five architecture decisions from the blueprint §9
(BINKY-WP-0007-T01): domain-assistant pattern, repo home, v1
no-spend policy freeze, MCP transport, vendor MCP as backend.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

DecisionQueue.md

@@ -30,7 +30,35 @@ fallback_if_no_response: ""
 
 ## Open decisions
 
-_(none)_
+### DEC-2026-005 — Qonto Governed Assistant: ratify Phase 1 architecture (BINKY-WP-0007-T01)
+
+```yaml
+id: DEC-2026-005
+title: "Adopt domain-assistant architecture for Qonto access; repo home; v1 policy freeze; MCP transport; vendor MCP as internal backend"
+lane: yellow
+status: prepared
+created_at: "2026-07-22"
+needed_by: ""
+attention_cost: "~5 min — five bundled yes/no calls, one per line below"
+agent_recommendation: "Approve all five as recommended (B / new qonto-assistant repo / hard freeze / streamable-HTTP only / no vendor MCP)."
+evidence:
+  - integrations/qonto-governed-assistant/ArchitectureBlueprint.md
+  - workplans/BINKY-WP-0007-qonto-governed-assistant.md
+  - integrations/qonto-mcp.md
+options: [approve, reject, revise, defer]
+fallback_if_no_response: "No Phase 1 build work starts (BINKY-WP-0007-T02+) until this resolves; T01 stays open."
+questions:
+  - q: "1. Adopt the domain-assistant architecture (blueprint option B: our own MCP+REST service owns the policy) over wiring vendor Qonto MCP into every harness, or a generic gateway alone?"
+    recommendation: "Approve option B — only approach that encodes semantic no-spend policy in one place."
+  - q: "2. Repo home for the assistant: new dedicated `qonto-assistant` repo (already present in the state-hub registry) vs. waiting for a future generic `finance-connect` monorepo?"
+    recommendation: "New `qonto-assistant` repo now — don't block dogfood on a monorepo that doesn't exist yet."
+  - q: "3. v1 policy freeze: hard deny on all spend / volume-cost tools (transfers, cards, invoicing sends, plan changes), no exceptions in this phase?"
+    recommendation: "Approve the freeze — matches existing Red-lane-forever stance from DEC-2026-004."
+  - q: "4. MCP transport: remote streamable-HTTP only for production clients (no local stdio in prod)?"
+    recommendation: "Approve — stdio only for local dev against the same binary."
+  - q: "5. Ever run vendor `qonto-mcp-server` as an internal-only backend behind our policy gate?"
+    recommendation: "No (blueprint default) — we already proved a direct REST client; fewer moving parts, no unmaintained vendor code in the trust boundary."
+```
 
 ## Resolved decisions