Bootstrap qonto-assistant: intent, blueprint, research, workplans

Author INTENT and SCOPE; persist ArchitectureBlueprint under specs/ and MCP
gateway research under research/. Register with State Hub (QONTO-WP- prefix);
seed QONTO-WP-0001 (bootstrap, finished) and QONTO-WP-0002 (Phase 1 REST
policy kernel, ready).

README.md

@@ -1,3 +1,25 @@
 # qonto-assistant
 
-A policy governed qonto domain API and MCP assistant for binky-control.
+Policy-governed Qonto domain API and MCP assistant for Binky (and later
+multi-tenant dogfood).
+
+**One choke point for bank access across every coding agent and harness.**
+Clients never hold the Qonto API key. v1 policy: **read for awareness only —
+no spend, no volume-cost actions.**
+
+## Start here
+
+| Doc | What |
+| --- | --- |
+| [`INTENT.md`](INTENT.md) | Why this exists; boundaries |
+| [`specs/ArchitectureBlueprint.md`](specs/ArchitectureBlueprint.md) | Architecture, phases, policy model |
+| [`research/2026-07-21-mcp-gateway-and-governed-domain-assistant.md`](research/2026-07-21-mcp-gateway-and-governed-domain-assistant.md) | External + internal research |
+
+## Status
+
+Scaffold + intent + blueprint. Implementation tracked in `workplans/`.
+
+## Related
+
+- OpenBao lane: `tenants/binky/qonto-api` (ops-warden `binky-qonto-api`)
+- First pull / CostRunRate: `binky-control` BINKY-WP-0005