mail triage 2026-07-18 (founder) + AWQ-010 Qonto MCP integration

- E-mail triage log section added: jamesandersons spam resolved by
  founder; IHK Sommerfest invitation (August, founder calendar call);
  Qonto MCP mailing -> actionable
- AWQ-010: Qonto MCP integration prep (read scopes first, ops-warden/
  OpenBao credential lane, no native integrations; complements DUO =
  DATEV Unternehmen Online as main accounting, does not replace it)
- OH-2026-003 enriched: MCP integration is an argument FOR keeping
  Qonto; check API/plan prerequisites while in the dashboard

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-18 17:03:07 +02:00
parent faca8019ba
commit 06afc317f1
3 changed files with 39 additions and 4 deletions

View file

@ -5,6 +5,26 @@
## Queue
```yaml
id: AWQ-010
title: "Qonto MCP integration: connect the company bank account to our agent infrastructure"
lane: green
pulls_from: [mailmeta/mail-log.md 2026-07-18, OH-2026-003]
notes: "Founder direction 2026-07-18: 'integrations like this should help
with the automated company approach a lot' — arrange soon. Prepare the
integration package: (a) Qonto MCP capabilities/docs review (read scopes
first; payments are Red-lane forever); (b) credential lane via ops-warden/
OpenBao (tenants/binky/qonto — same custody pattern as company-email;
provisioning founder Red lane; NO claude.ai native integrations, harness/
MCP lane only); (c) consumer design: rhythm sessions + finance/
CostRunRate.md feeds (real balance/transactions replace manual Qonto
pulls, part of OH-2026-003's cost-vs-usage answer — the MCP is an
argument FOR keeping Qonto); (d) note main accounting stays DATEV
Unternehmen Online (DUO) — Qonto MCP complements, does not replace,
the DUO/StB lane. Output: integrations/qonto-mcp.md design + DecisionQueue
entry for the Red-lane provisioning."
```
```yaml
id: AWQ-002
title: "Map self-billed Eigenentwicklung invoices to ecosystem capabilities as IP evidence"

View file

@ -42,7 +42,11 @@ id: OH-2026-003
title: "Qonto account review: cost vs. usage, access verification"
counterparty: bank
status: prepared
prepared_material: []
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."]
deadline_pressure: none
```

View file

@ -1,7 +1,18 @@
# Paper-Mail Log
# Mail Log
> Metadata only — scan contents never enter this repo. Pipeline:
> `integrations/paper-mail-intake.md`. One row per item, newest first.
> Metadata only — message/scan contents never enter this repo. Paper
> pipeline: `integrations/paper-mail-intake.md`; e-mail triage lands here
> too (harness mail-intake task). One row per item, newest first.
## E-mail triage log
| Date | Sender/Topic | Outcome |
|------|--------------|---------|
| 2026-07-18 | Qonto mailing: Qonto MCP — integrate bank account with own AI infrastructure | Actionable → AWQ-010 (integration prep); supports keeping Qonto despite cost (feeds OH-2026-003) |
| 2026-07-18 | IHK: invitation Sommerfest (August 2026) | Founder calendar decision — attend/skip; exact date in the mail |
| 2026-07-18 | jamesandersons76890@gmail.com (2 msgs, flagged 2026-07-17) | Resolved by founder: classified spam, removed from mailbox. Never acted on content. |
## Paper-Mail Log
| Date | Sender | Type | Deadline | Routed to | Archive |
|------|--------|------|----------|-----------|---------|