coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source 
- 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
Download patch file Download diff file Expand all files Collapse all files

14
OfficeHourQueue.md
View file

@ -43,10 +43,16 @@ title: "Qonto account review: cost vs. usage, access verification"
counterparty: bank
status: prepared
prepared_material: ["2026-07-18: Qonto announced MCP integration (mailing) —
connecting the account to our agent infrastructure is planned (AWQ-010)
and is a substantive argument FOR keeping Qonto despite plan cost.
While in the dashboard: check API/MCP access prerequisites and plan tier
requirements."]
connecting the account to our agent infrastructure is planned (AWQ-010
→ BINKY-WP-0005) and is a substantive argument FOR keeping Qonto despite
plan cost. While in the dashboard: check API/MCP access prerequisites and
plan tier requirements.",
"2026-07-19: DEC-2026-004 APPROVED — execute the Red-lane provisioning
while in the dashboard: create API key under /settings/integrations, note
organization ID, then bao kv put per the founder-provision block in
integrations/qonto-mcp.md. Also note plan tier + monthly fee for
finance/CostRunRate.md row 4. Unblocks BINKY-WP-0005-T05 (first
read-only pull)."]
deadline_pressure: none
```