DEC-2026-004 approved: Qonto provisioning scheduled for next office hour

- DecisionQueue: DEC-2026-004 → resolved (approved, Bernd, 2026-07-19);
  hub decision a2a9de69 resolved
- OH-2026-003 enriched with the Red-lane provisioning steps (API key +
  bao kv put per integrations/qonto-mcp.md) for the dashboard visit
- qonto-mcp.md checklist: approval done, provisioning next

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-19 14:31:02 +02:00
parent a95dc29a73
commit ff579be1aa
3 changed files with 29 additions and 24 deletions

View file

@ -99,10 +99,12 @@ Rules:
1. [x] Variant + read-only enforcement decided (this doc)
2. [x] OpenBao lane designed (`tenants/binky/qonto/api`)
3. [x] DecisionQueue package prepared (DEC-2026-004)
4. [ ] **Red lane — founder:** approve DEC-2026-004; create API key; `bao kv put` via `@file`
5. [ ] Warden catalog `binky-qonto-api` draft → active after provision
6. [ ] First read-only pull; update CostRunRate TBC rows (BINKY-WP-0005-T05)
7. [ ] Wire Finance Steward recurring session (post-cutover, harness lane)
4. [x] DEC-2026-004 **approved** (founder, 2026-07-19)
5. [ ] **Red lane — founder (next office hour, with OH-2026-003):** create
API key; `bao kv put` via `@file`
6. [ ] Warden catalog `binky-qonto-api` draft → active after provision
7. [ ] First read-only pull; update CostRunRate TBC rows (BINKY-WP-0005-T05)
8. [ ] Wire Finance Steward recurring session (post-cutover, harness lane)
## See also