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

Draft BINKY-WP-0003: Autopilot Execution & Recurring Rhythm

Browse source 
Six tasks: OpenBao email onboarding, audit template v1, cost table,
workstation-cron bridge scheduler, activity-core wiring, llm-connect
assessment as workstation-independent executor (with kaizen-agentic).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-16 10:37:36 +02:00
parent e287b90510
commit 69e2d05aa3
1 changed files with 93 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

93
workplans/BINKY-WP-0003-autopilot-and-rhythm.md Normal file
View file

@ -0,0 +1,93 @@
---
id: BINKY-WP-0003
title: "Autopilot Execution & Recurring Rhythm"
status: active
---
Turn the operating rhythm from pull-based (founder-initiated sessions) into
scheduled, then event-driven execution. Near-term: work off the highest-value
AutopilotWorkQueue items and bridge scheduling with a workstation cron.
End state: activity-core triggers the rhythm and llm-connect executes it
**independently of this workstation**, with kaizen-agentic providing the agent
personas — real automated work driven by real-world events (company email,
paper mail, hub state). Successor to BINKY-WP-0002.
## Task: Onboard company email into Net Kingdom / OpenBao (AWQ-007)
Prepare the OpenBao vault path and integration plan for
bernd.worsch@binky-hedgehog.com; wire the mailbox toward the agent event loop
(email-connect capability). Credential handover from the founder is a single
Red-lane step at the end — everything else is Blue-lane preparation. Goal:
StB replies and bank/authority notices reach the control plane.
```task
id: BINKY-WP-0003-T01
status: todo
priority: high
```
## Task: Generalize audit template v1 from the Binky run (AWQ-001)
Turn audits/OK-Audit-v0-binky.md into a customer-ready, company-agnostic
audit template v1 (candidate home: audit-core repo; keep a copy in this
repo). Flagship-offer dependency (OfferCatalog.md). Green lane.
```task
id: BINKY-WP-0003-T02
status: todo
priority: medium
```
## Task: Consolidated cost & run-rate table (AWQ-004)
Desk, Qonto, DATEV, Stripe, infra: one table with monthly run-rate, feeding
the cash/runway view (Finance Steward loop). Sources: audit v0, DUO once
accessible, founder confirmation for gaps. Green lane.
```task
id: BINKY-WP-0003-T03
status: todo
priority: medium
```
## Task: Bridge scheduler — workstation cron for the operating rhythm
Schedule a recurring Claude Code session on this workstation that runs queue
hygiene, writes the daily brief, and pulls one autopilot item when idle
(OperatingRhythm.md). Explicitly a **bridge** until T05/T06 land; document
the schedule and how to disable it. Blue lane.
```task
id: BINKY-WP-0003-T04
status: todo
priority: high
```
## Task: Wire binky-control rhythm into activity-core
Write activity-definitions for the recurring items (daily brief + queue
hygiene, weekly paper-mail intake check AWQ-008, weekly review) so scheduling
lives in the sanctioned coordination layer. Verify activity-core deployment
state and where dispatched work items land. Green/Blue lane.
```task
id: BINKY-WP-0003-T05
status: todo
priority: medium
```
## Task: Assess llm-connect as workstation-independent executor
**Note (founder, 2026-07-16):** llm-connect should enable real automated work
triggered by activity-core, running independently from this workstation — and
should connect well with kaizen-agentic (agent personas from the hub).
Assess: current llm-connect capability, how activity-core dispatch reaches
it, how a kaizen-agentic persona is loaded into an llm-connect execution, and
what secrets/access it needs (OpenBao, T01 groundwork). Output: architecture
note + follow-up workplan proposal. Green lane (assessment only).
```task
id: BINKY-WP-0003-T06
status: todo
priority: medium
```