binky-control/OfficeHourQueue.md

Office-Hour Queue

Status: live document — Orange-lane items that need business-hour interaction (calls, banks, authorities, accountant, notary). Batched into ~two office-hour command days per month. Agents preload each day with a runbook; the day is scarce strategic infrastructure — protect it from low-leverage work.

Closing an item (CUST-WP-0061-T05, 2026-07-21): set status: done directly on the item's own yaml block in place — it already stays under "## Queued items" as the historical record; no separate log to move it to. WORK-RECORDS.md (generated by statehub fix-consistency) is the always-current cross-cutting view of every engagement including done ones.

Item template

id: OH-2026-NNN
title: ""
counterparty: ""        # accountant, bank, authority, customer, vendor
status: queued | prepared | done
prepared_material: []   # briefings, drafts, documents ready before the call
deadline_pressure: none | soft | hard (date)

Queued items

id: OH-2026-001
title: "Follow up StB inquiry with Inga Bohle-Horsmann (mandate for JA 2025+)"
counterparty: accountant
status: prepared
prepared_material: [audits/OK-Audit-v0-binky.md, "inquiry email 2026-07-06", "JA 2024 report PDF"]
deadline_pressure: soft (early August 2026 — she returns end of July)

id: OH-2026-002
title: "DUO receipt-backlog catch-up and license/access transition plan"
counterparty: accountant
status: prepared
prepared_material: ["Weglarzy agreed to accompany DUO transfer"]
deadline_pressure: soft (before new mandate starts)

id: OH-2026-003
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
  → 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).",
  "2026-07-21: Lane scaffolding ready — CCR-2026-0008 (draft) + policy HCL
  in railiance-platform; ops-warden catalog binky-qonto-api (draft) +
  playbook; copy-paste OH/T05 runbook in integrations/qonto-mcp.md and
  officehour/2026-08-command-day-runbook.md. Only Red-lane provision +
  CCR apply remain before first pull."]
deadline_pressure: none

id: OH-2026-004
title: "Verify Handelsregister entry, registered address, Unternehmensgegenstand; locate articles of association"
counterparty: authority
status: prepared
prepared_material: []
deadline_pressure: none

id: OH-2026-005
title: "Stripe dashboard: delete stale webhook endpoint https://api.preprod.blobr.dev"
counterparty: bank
status: prepared
prepared_material: ["AWQ-009 diagnosis: endpoint from defunct Blobr integration,
  DNS no longer resolves (blobr.dev gone); Stripe has sent monthly failure
  digests on the 5th since April 2026. Steps: Stripe Dashboard → Developers →
  Webhooks → delete the api.preprod.blobr.dev endpoint. While there: list any
  OTHER webhook endpoints + confirm which are live for the subscription
  pipeline (needed for AWQ-002-adjacent revenue infra inventory)."]
deadline_pressure: "low — but Stripe auto-disables chronically failing endpoints;
  cleanup avoids noise masking a real failure"

Office-Hour Runbook template

# Office-Hour Command Day — <date>

## Must do today
1. ...

## Prepared material
- ...

## Do not spend time on
- internal documentation
- repo cleanup
- speculative naming