binky-control/officehour/2026-08-command-day-runbook.md
tegwick 74cc9a5ed1
All checks were successful
Work Records / validate (push) Successful in 7s
Schedule OH command day for Sunday 2026-08-16; resequence for a Sunday
Original first-half-of-August window lapsed at 0/5. Founder set 2026-08-16.

Sunday changes the plan: the Bohle-Horsmann office is closed, so OH-2026-001
loses its phone option. It becomes an email dispatched FIRST (landing Monday
morning) rather than an item that closes on the day, and RISK-006 moves to
'awaiting counterparty reply' rather than mitigated. Follow-up slot Tue
2026-08-18 for call-or-fallback. Expected day result: 4/5 closed, 001 pending.

Also adds OH-2026-005, which was missing from the must-do list, and a
Sunday-appropriate running order.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-16 01:24:22 +02:00

103 lines
5.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Office-Hour Command Day — Sunday 2026-08-16, afternoon (scheduled)
> First command day of the reactivation. **Scheduled 2026-08-16 afternoon.**
> The original "first two weeks of August" window lapsed at 0/5 drained.
> All items sourced from OK Audit v0 findings (`audits/OK-Audit-v0-binky.md`).
## Sunday constraint — read before starting
This is a **Sunday**. Four of the five items are self-service digital and work
fine (DUO, Qonto, handelsregister.de, Stripe). **OH-2026-001 does not** — the
Bohle-Horsmann office is closed and the phone (03843-72110) is not an option
today.
Consequence: **001 gets dispatched today, not resolved today.** Send the email
*first*, so it is at the top of Inga's inbox Monday morning rather than behind a
weekend backlog; then spend the rest of the afternoon on the four items that do
close. RISK-006 therefore **cannot** leave "unmitigated" today — it moves to
"awaiting counterparty reply", with a follow-up call slot on **Tue 2026-08-18**
if nothing has come back by then.
Realistic outcome of this day: **4/5 closed, 001 dispatched.**
## Must do today
1. **OH-2026-001 — Email Inga Bohle-Horsmann FIRST**
(horsmann@bohle-horsmann.de; phone 03843-72110 unusable today): does she
take the mandate?
- Reply into the existing 2026-07-06 thread rather than opening a new one —
she already has the JA 2024 PDF from it.
- State the scope in the mail so a yes is a complete yes: JA 2025 + ongoing
filings, "notify me when something is due" mode, DUO takeover accompanied
by Weglarzy. Ask for a yes/no plus an earliest-start date.
- If no (or no reply by **Tue 2026-08-18**): fallback decision — re-engage
Weglarzy/FSW (06151-…, Landwehrstr. 54, Darmstadt) or search alternative.
- Mark OH-2026-001 `dispatched`, not `done`. It closes when she replies.
2. **OH-2026-002 — DUO Belegablage**: log in, assess receipt backlog size,
photograph/upload missing receipts. Note: *confirming access continuity
through the mandate transition* depends on 001 and is deferred with it —
size and clear the backlog today regardless, since that work is needed under
any StB outcome.
3. **OH-2026-003 — Qonto** (DEC-2026-004 approved — **also Red-lane provision**):
- Verify dashboard access works.
- Note plan tier + monthly fee → `finance/CostRunRate.md` row 4.
- Note cheaper plan options (plan *change* itself can wait — data only).
- **Provision API key for MCP (unblocks BINKY-WP-0005-T05):**
1. `/settings/integrations` → create API key; note organization ID.
2. Private terminal only (never chat/agent):
```bash
umask 077
# key → /tmp/qonto.key, org id → /tmp/qonto.org
bao kv put tenants/binky/qonto/api \
QONTO_API_KEY=@/tmp/qonto.key \
QONTO_ORGANIZATION_ID=@/tmp/qonto.org
shred -u /tmp/qonto.key /tmp/qonto.org
```
3. Full procedure: `integrations/qonto-mcp.md` (OH/T05 runbook).
4. After provision: agent runs first read-only pull + CostRunRate update.
4. **OH-2026-004 — Handelsregister**: pull current HR excerpt
(handelsregister.de), verify registered address and GF details, download
articles of association if retrievable; file everything in `2binky/`.
Full prep (free retrieval path, the four fields to verify, filing rule,
Orange/Red boundary) is in `OfficeHourQueue.md` under OH-2026-004.
5. **OH-2026-005 — Stripe webhook cleanup**: Dashboard → Developers →
Webhooks → delete the stale `api.preprod.blobr.dev` endpoint; while there,
list remaining endpoints and confirm which are live.
## Suggested order for a Sunday afternoon
1. **001 email** (~15 min) — send first, it needs to sit in an inbox overnight
2. **005** (510 min) — clears the monthly failure-digest noise
3. **004** (1525 min) — register pull, independent of the StB question
4. **003** (3045 min) — Qonto review + API provision (private terminal)
5. **002** (open-ended) — DUO backlog; the item most likely to overrun, so it
goes last and can be truncated without blocking anything else
## Prepared material
- `audits/OK-Audit-v0-binky.md` — one-page situation summary for any call
- Inquiry email thread 2026-07-06 (`~/2binky/260706a-mandatsanfrageIngaBohle/`)
- JA 2024 report PDF (same folder) — already shared with Inga
- Talking points for the StB contact (now an email, see item 1): small mandate,
JA + formal filings, proactive deadline notification wanted, DUO takeover
accompanied by Weglarzy
## Do not spend time on
- internal documentation, repo cleanup, speculative naming
- Qonto plan *change* (data gathering only — change is a separate Red-lane step)
- website/domain decisions (queued as AWQ-003/AWQ-005, not office-hour work)
## After the day
Update OfficeHourQueue item statuses, RiskRegister (RISK-006/007), and the
CompanyReactivationPlan checklist; write the daily brief.
Then update the project-side tracker
`prj-unattended-progress-company/evidence/g1-oh-batch.md` (UPC-WP-0002-T01) and
the G1/G8 rows in `architecture/gate-map.md` (T02). With 001 still open, the S1
decision package (`evidence/s1-decision-package.md`) stays draft — S1 is not
markable until the StB mandate question has an answer.
**Open follow-up after the day:** Tue 2026-08-18 — if Inga has not replied,
call 03843-72110 or trigger the Weglarzy/FSW fallback.